2023-04-29T13:15:52.50026+08:00 INFO [359133,d8742349c0f00883] caller=stat/metrics.go:25:RegisterStat: registry with labels: map[app:HOST process:ob_monagent svr_ip:10.0.10.102] 2023-04-29T13:15:52.50176+08:00 INFO [359133,d8742349c0f00883] caller=stat/metrics.go:25:RegisterStat: registry with labels: map[app:HOST process:ob_monagent svr_ip:10.0.10.102] 2023-04-29T13:15:52.50791+08:00 INFO [359133,d8742349c0f00883] caller=sdk/monagent_callbacks.go:75:func6: module monagent.server.basic.auth init config successfully 2023-04-29T13:15:52.51686+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields: module=ob.custom, duration="14.9µs" 2023-04-29T13:15:52.51695+08:00 INFO [359133,d8742349c0f00883] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields:, module=ob.custom, eventType=add, duration="5.2µs" 2023-04-29T13:15:52.51701+08:00 INFO [359133,d8742349c0f00883] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields:, module=ob.custom, duration="3.8µs" 2023-04-29T13:15:52.51705+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields:, module=ob.custom, eventType=add, duration="4.3µs" 2023-04-29T13:15:52.51708+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:48:init: init input instance dbConnectivityInput 2023-04-29T13:15:52.51722+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:48:init: init input instance processInput 2023-04-29T13:15:52.51732+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:48:init: init input instance hostCustomInput 2023-04-29T13:15:52.51799+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:62:init: init processor instance attrProcessor 2023-04-29T13:15:52.51833+08:00 INFO [359133,d8742349c0f00883] caller=attr/attribute_operate.go:61:Init: init retagProcessor with config: {Operations:[{Oper:addTags Condition:{Metric: Fields:map[] Tags:map[]} Tags:map[app:OB ob_cluster_id:1 ob_cluster_name:fund obzone:zone1 svr_ip:10.0.10.102 svr_port:2882] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:io_util Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:io_await Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:node_net_bandwidth_bps Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:node_ntp_offset_seconds Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:ssd_wear_indicator Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:tcp_retrans Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:cpu_count Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]}]} 2023-04-29T13:15:52.51839+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:90:init: init exporter instance prometheusExporter 2023-04-29T13:15:52.51846+08:00 INFO [359133,d8742349c0f00883] caller=prometheus/prometheus.go:78:Init: prometheus exporter config: &{FormatType:fmtText ExposeUrl: WithTimestamp:false} 2023-04-29T13:15:52.51856+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields: module=ob.custom, eventType=add, duration=1.512921ms 2023-04-29T13:15:52.54081+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for io_infos updated firstly! 2023-04-29T13:15:52.54289+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for cpu_count updated firstly! 2023-04-29T13:15:52.55679+08:00 INFO [359133,d8742349c0f00883] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields:, module=ob.custom, duration=39.791865ms 2023-04-29T13:15:52.55683+08:00 INFO [359133,d8742349c0f00883] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields:, module=ob.custom, eventType=add, duration=39.885267ms 2023-04-29T13:15:52.55687+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_module_callback.go:38:addPipeline: add pipeline module config result status: succeed, description: fields:, module=ob.custom, duration=40.022568ms 2023-04-29T13:15:52.5569+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_module_callback.go:126:func1: add pipeline module config ob.custom successfully. 2023-04-29T13:15:52.56846+08:00 WARN [359133,d8742349c0f00883] caller=engine/pipeline_module_callback.go:119:InitPipelineModuleCallback: pipeline module config monitor.mysql is inactive or invalid, just skip 2023-04-29T13:15:52.56916+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields:, module=monitor.node.host, duration="13.2µs" 2023-04-29T13:15:52.56921+08:00 INFO [359133,d8742349c0f00883] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields:, module=monitor.node.host, eventType=add, duration="10.3µs" 2023-04-29T13:15:52.56923+08:00 INFO [359133,d8742349c0f00883] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields: module=monitor.node.host, duration="4.2µs" 2023-04-29T13:15:52.56931+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields: module=monitor.node.host, eventType=add, duration="30.9µs" 2023-04-29T13:15:52.56934+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:48:init: init input instance nodeExporterInput 2023-04-29T13:15:52.57007+08:00 INFO [359133,] caller=collector/filesystem_common.go:110:NewFilesystemCollector: fields: fields.level=info, flag="^/(dev|proc|sys|var/lib/docker/.+)($|/)", fields.msg="Parsed flag --collector.filesystem.mount-points-exclude", collector=filesystem 2023-04-29T13:15:52.57016+08:00 INFO [359133,] caller=collector/filesystem_common.go:112:NewFilesystemCollector: fields:, fields.msg="Parsed flag --collector.filesystem.fs-types-exclude", fields.level=info, flag="^(autofs|binfmt_misc|bpf|cgroup2?|configfs|debugfs|devpts|devtmpfs|fusectl|hugetlbfs|iso9660|mqueue|nsfs|overlay|proc|procfs|pstore|rpc_pipefs|securityfs|selinuxfs|squashfs|sysfs|tracefs)$", collector=filesystem 2023-04-29T13:15:52.57046+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:62:init: init processor instance aggregateProcessor 2023-04-29T13:15:52.57074+08:00 INFO [359133,d8742349c0f00883] caller=aggregate/aggregator.go:73:Init: init aggregateProcessor with config: &{Rules:[0xc00065bd70] IsRetainNativeMetric:false} 2023-04-29T13:15:52.57077+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:62:init: init processor instance attrProcessor 2023-04-29T13:15:52.57105+08:00 INFO [359133,d8742349c0f00883] caller=attr/attribute_operate.go:61:Init: init retagProcessor with config: {Operations:[{Oper:copyTags Condition:{Metric: Fields:map[] Tags:map[]} Tags:map[mountpoint:mount_point] RemoveItems:[]} {Oper:addTags Condition:{Metric: Fields:map[] Tags:map[]} Tags:map[app:HOST ob_cluster_id:1 ob_cluster_name:fund obproxy_cluster: obproxy_cluster_id:0 obzone:zone1 svr_ip:10.0.10.102] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:node_filesystem_size_bytes Fields:map[] Tags:map[fstype:tmpfs]} Tags:map[] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:node_filesystem_avail_bytes Fields:map[] Tags:map[fstype:tmpfs]} Tags:map[] RemoveItems:[]}]} 2023-04-29T13:15:52.57108+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:62:init: init processor instance mountLabelProcessor 2023-04-29T13:15:52.5712+08:00 INFO [359133,d8742349c0f00883] caller=label/mount_label.go:70:Init: init mountLabelProcessor with config: &{LabelTags:map[checkReadonly:/ dataDiskPath:/home/oceanbase/fund/oceanbase/store installPath:/home/oceanbase/fund/oceanbase logDiskPath:/home/oceanbase/fund/oceanbase/store] ObStatus:active} 2023-04-29T13:15:52.57977+08:00 INFO [359133,] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=df /home/oceanbase/fund/oceanbase, timeout=10s}, exitCode=1 fields:, duration=8.500321ms 2023-04-29T13:15:52.57984+08:00 WARN [359133,] caller=common/mount.go:22:GetMountPath: get path's mount failed, filePath: /home/oceanbase/fund/oceanbase 2023-04-29T13:15:52.58671+08:00 INFO [359133,] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=df /data/fund, timeout=10s}, exitCode=1 fields: duration=6.848097ms 2023-04-29T13:15:52.58675+08:00 WARN [359133,] caller=common/mount.go:22:GetMountPath: get path's mount failed, filePath: /data/fund 2023-04-29T13:15:52.59321+08:00 INFO [359133,] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=df /data/fund, timeout=10s}, exitCode=1 fields: duration=6.443592ms 2023-04-29T13:15:52.59326+08:00 WARN [359133,] caller=common/mount.go:22:GetMountPath: get path's mount failed, filePath: /data/fund 2023-04-29T13:15:52.60431+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields:, module=monitor.ob, duration="15.8µs" 2023-04-29T13:15:52.61456+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for filesystem updated firstly! 2023-04-29T13:15:52.61473+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for netdev updated firstly! 2023-04-29T13:15:52.61549+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for cpu updated firstly! 2023-04-29T13:15:52.61559+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for oceanbase_connectivity updated firstly! 2023-04-29T13:15:52.61562+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for loadavg updated firstly! 2023-04-29T13:15:52.61571+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for meminfo updated firstly! 2023-04-29T13:15:52.61584+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for diskstats updated firstly! 2023-04-29T13:15:52.61598+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=ethtool lo, timeout=50s}, exitCode=1 fields: duration=72.785734ms 2023-04-29T13:15:52.61601+08:00 WARN [359133,d8742349c0f00883] caller=host/custom.go:475:doCollectBandwidthInfo: get bandwidth of net interface lo failed, cmd: ethtool lo 2023-04-29T13:15:52.62399+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=ethtool eth0, timeout=50s}, exitCode=1 fields: duration=7.973213ms 2023-04-29T13:15:52.62403+08:00 WARN [359133,d8742349c0f00883] caller=host/custom.go:475:doCollectBandwidthInfo: get bandwidth of net interface eth0 failed, cmd: ethtool eth0 2023-04-29T13:15:52.62405+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for bandwidth_infos updated firstly! 2023-04-29T13:15:52.62502+08:00 WARN [359133,d8742349c0f00883] caller=engine/pipeline_module_callback.go:119:InitPipelineModuleCallback: pipeline module config host.log is inactive or invalid, just skip 2023-04-29T13:15:52.62594+08:00 WARN [359133,d8742349c0f00883] caller=engine/pipeline_module_callback.go:119:InitPipelineModuleCallback: pipeline module config trace.log is inactive or invalid, just skip 2023-04-29T13:15:52.6283+08:00 WARN [359133,d8742349c0f00883] caller=engine/pipeline_module_callback.go:119:InitPipelineModuleCallback: pipeline module config monitor.ob.err.log is inactive or invalid, just skip 2023-04-29T13:15:52.6292+08:00 WARN [359133,d8742349c0f00883] caller=engine/pipeline_module_callback.go:119:InitPipelineModuleCallback: pipeline module config ob.log is inactive or invalid, just skip 2023-04-29T13:15:52.62959+08:00 INFO [359133,] caller=config/config_version.go:34:SetConfigMetaModuleConfigNotify: receive version backup conf: {MaxBackups:30} 2023-04-29T13:15:52.62981+08:00 INFO [359133,] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=df /, timeout=10s}, exitCode=1 fields: duration=36.536118ms 2023-04-29T13:15:52.62987+08:00 WARN [359133,] caller=common/mount.go:22:GetMountPath: get path's mount failed, filePath: / 2023-04-29T13:15:52.63784+08:00 INFO [359133,] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=df -h, timeout=10s}, exitCode=1 fields:, duration=7.910913ms 2023-04-29T13:15:52.63789+08:00 WARN [359133,d8742349c0f00883] caller=label/mount_label.go:187:getMountPV: execute cmd df -h failed, err: failed to execute command: Command{user=admin, program=sh, outputType=combined, cmd=df -h, timeout=10s}, exitCode: 1, output: 2023-04-29T13:15:52.63791+08:00 WARN [359133,d8742349c0f00883] caller=engine/plugin_instance.go:68:init: get mountPV failed 2023-04-29T13:15:52.63792+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:90:init: init exporter instance prometheusExporter 2023-04-29T13:15:52.63799+08:00 INFO [359133,d8742349c0f00883] caller=prometheus/prometheus.go:78:Init: prometheus exporter config: &{FormatType:fmtText ExposeUrl: WithTimestamp:true} 2023-04-29T13:15:52.63801+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields:, module=monitor.node.host, eventType=add, duration=68.732176ms 2023-04-29T13:15:52.64981+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields:, module=log.alarm, duration="14.901µs" 2023-04-29T13:15:52.64988+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields: duration="7.4µs", module=node.custom 2023-04-29T13:15:52.6499+08:00 INFO [359133,] caller=runtime/asm_amd64.s:1581:goexit: check config version backups once. 2023-04-29T13:15:52.64999+08:00 INFO [359133,] caller=config/config_version.go:89:checkConfigVersionBackups: read config from path /home/oceanbase/fund/obagent/conf, files length 11 2023-04-29T13:15:52.65001+08:00 INFO [359133,] caller=config/config_version.go:105:checkConfigVersionBackups: config stay count:30, config version count:1, no need to rotate. 2023-04-29T13:15:52.65044+08:00 INFO [359133,d8742349c0f00883] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields: module=monitor.node.host, duration=81.209453ms 2023-04-29T13:15:52.65047+08:00 INFO [359133,d8742349c0f00883] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields: module=monitor.node.host, eventType=add, duration=81.269954ms 2023-04-29T13:15:52.65049+08:00 INFO [359133,d8742349c0f00883] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields:, module=monitor.ob, eventType=add, duration="5.1µs" 2023-04-29T13:15:52.65051+08:00 INFO [359133,d8742349c0f00883] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields:, module=monitor.ob, duration="3.701µs" 2023-04-29T13:15:52.65055+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields:, module=monitor.ob, eventType=add, duration="4.2µs" 2023-04-29T13:15:52.65057+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-04-29T13:15:52.65603+08:00 INFO [359133,d8742349c0f00883] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc0002201e0 0xc000220280 0xc000220320 0xc0002203c0 0xc000220460 0xc000220500 0xc0002205a0 0xc000220640 0xc0002206e0 0xc000220780 0xc000220820 0xc0002208c0 0xc000220960 0xc000220a00 0xc000220aa0 0xc000220b40 0xc000220be0 0xc000220c80 0xc000220d20 0xc000220dc0 0xc000220e60 0xc000220f00 0xc000220fa0 0xc000221040 0xc0002210e0 0xc000221180 0xc000221220 0xc0002212c0 0xc000221360 0xc000221400 0xc0002214a0] CollectInterval:1s TimeAlign:false} 2023-04-29T13:15:52.65662+08:00 INFO [359133,d8742349c0f00883] caller=monagent/monagent_route.go:77:RegisterPipelineRoute: register route /metrics/node/ob 2023-04-29T13:15:52.65665+08:00 INFO [359133,d8742349c0f00883] caller=monagent/monagent_route.go:77:RegisterPipelineRoute: register route /metrics/node/ob 2023-04-29T13:15:52.65667+08:00 INFO [359133,d8742349c0f00883] caller=monagent/monagent_route.go:77:RegisterPipelineRoute: register route /metrics/node/host 2023-04-29T13:15:52.65669+08:00 INFO [359133,d8742349c0f00883] caller=monagent/monagent_route.go:77:RegisterPipelineRoute: register route /metrics/node/host 2023-04-29T13:15:52.65673+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_module_callback.go:38:addPipeline: add pipeline module config result status: succeed, description: fields: duration=87.583444ms, module=monitor.node.host 2023-04-29T13:15:52.65676+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_module_callback.go:126:func1: add pipeline module config monitor.node.host successfully. 2023-04-29T13:15:52.70982+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for process updated firstly! 2023-04-29T13:15:52.71816+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.263517ms 2023-04-29T13:15:52.71826+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:15:52.71829+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for node_ntp_offset_seconds updated firstly! 2023-04-29T13:15:52.74568+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:54:init: successfully init mysqlTableInput plugin 2023-04-29T13:15:52.74572+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:62:init: init processor instance retagProcessor 2023-04-29T13:15:52.74586+08:00 INFO [359133,d8742349c0f00883] caller=retag/retag.go:63:Init: init retagProcessor with config: &{RenameTags:map[] CopyTags:map[] NewTags:map[app:OB ob_cluster_id:1 ob_cluster_name:fund obzone:zone1 svr_ip:10.0.10.102 svr_port:2882]} 2023-04-29T13:15:52.74588+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:62:init: init processor instance jointable 2023-04-29T13:15:52.74667+08:00 INFO [359133,d8742349c0f00883] caller=jointable/jointable.go:137:Init: init JoinTablePluginConfig with config: &{DbConnectionConfig:{Url:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true MaxOpen:32 MaxIdle:2} JoinTableConfigs:[{QueryDataConfigs:[{QuerySQL:SELECT tenant_id ob_tenant_id, tenant_name FROM __all_tenant QueryArgs:[] MinOBVersion: MaxOBVersion:4.0.0.0}] CacheExpire:3m0s Conditions:[{Metrics:[ob_cache ob_partition ob_table ob_plan_cache ob_waitevent ob_system_event ob_tenant_task ob_clog ob_memstore ob_compaction ob_unit_config ob_tenant_unit ob_system_event_detail ob_latch ob_tenant ob_tenant_server ob_tenant_server_available] metrics:map[] Tags:map[] TagNames:[ob_tenant_id] RemoveNotMatchedTagValueMessage:true}]} {QueryDataConfigs:[{QuerySQL:SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META' QueryArgs:[] MinOBVersion:4.0.0.0 MaxOBVersion:}] CacheExpire:3m0s Conditions:[{Metrics:[ob_cache ob_partition ob_table ob_plan_cache ob_waitevent ob_system_event ob_tenant_task ob_clog ob_memstore ob_compaction ob_unit_config ob_tenant_unit ob_system_event_detail ob_latch] metrics:map[] Tags:map[] TagNames:[ob_tenant_id] RemoveNotMatchedTagValueMessage:true}]} {QueryDataConfigs:[{QuerySQL:SELECT tenant_id ob_tenant_id, tenant_name FROM __all_tenant QueryArgs:[] MinOBVersion: MaxOBVersion:4.0.0.0}] CacheExpire:3m0s Conditions:[{Metrics:[ob_sysstat] metrics:map[] Tags:map[] TagNames:[ob_tenant_id] RemoveNotMatchedTagValueMessage:false}]} {QueryDataConfigs:[{QuerySQL:SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META' QueryArgs:[] MinOBVersion:4.0.0.0 MaxOBVersion:}] CacheExpire:3m0s Conditions:[{Metrics:[ob_sysstat] metrics:map[] Tags:map[] TagNames:[ob_tenant_id] RemoveNotMatchedTagValueMessage:false}]}]} 2023-04-29T13:15:52.75763+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_server_resource updated firstly! 2023-04-29T13:15:52.76063+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_plan_cache updated firstly! 2023-04-29T13:15:52.76071+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:68:init: successfully init mysqlTableInput plugin 2023-04-29T13:15:52.76074+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:90:init: init exporter instance prometheusExporter 2023-04-29T13:15:52.76084+08:00 INFO [359133,d8742349c0f00883] caller=prometheus/prometheus.go:78:Init: prometheus exporter config: &{FormatType:fmtText ExposeUrl: WithTimestamp:false} 2023-04-29T13:15:52.76086+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-04-29T13:15:52.76304+08:00 INFO [359133,d8742349c0f00883] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc0002ec820 0xc0002ec8c0 0xc0002ec960 0xc0002eca00 0xc0002ecaa0 0xc0002ecb40 0xc0002ecbe0 0xc0002ecc80 0xc0002ecd20 0xc0002ecdc0 0xc0002ece60 0xc0002ecf00 0xc0002ecfa0 0xc0002ed040 0xc0002ed0e0 0xc0002ed180 0xc0002ed220 0xc0002ed2c0] CollectInterval:1m0s TimeAlign:false} 2023-04-29T13:15:52.76326+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_role updated firstly! 2023-04-29T13:15:52.7633+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for jointable-0 updated firstly! 2023-04-29T13:15:52.76342+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for jointable-2 updated firstly! 2023-04-29T13:15:52.76364+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_server updated firstly! 2023-04-29T13:15:52.77528+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_active_session updated firstly! 2023-04-29T13:15:52.77567+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_all_session updated firstly! 2023-04-29T13:15:52.77687+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_cache updated firstly! 2023-04-29T13:15:52.77816+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_waitevent updated firstly! 2023-04-29T13:15:52.77865+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_sysstat updated firstly! 2023-04-29T13:15:52.77873+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:54:init: successfully init mysqlTableInput plugin 2023-04-29T13:15:52.77875+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:62:init: init processor instance retagProcessor 2023-04-29T13:15:52.77889+08:00 INFO [359133,d8742349c0f00883] caller=retag/retag.go:63:Init: init retagProcessor with config: &{RenameTags:map[] CopyTags:map[] NewTags:map[app:OB ob_cluster_id:1 ob_cluster_name:fund obzone:zone1 svr_ip:10.0.10.102 svr_port:2882]} 2023-04-29T13:15:52.77912+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:62:init: init processor instance jointable 2023-04-29T13:15:52.78073+08:00 INFO [359133,d8742349c0f00883] caller=jointable/jointable.go:137:Init: init JoinTablePluginConfig with config: &{DbConnectionConfig:{Url:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true MaxOpen:32 MaxIdle:2} JoinTableConfigs:[{QueryDataConfigs:[{QuerySQL:SELECT tenant_id ob_tenant_id, tenant_name FROM __all_tenant QueryArgs:[] MinOBVersion: MaxOBVersion:4.0.0.0}] CacheExpire:3m0s Conditions:[{Metrics:[ob_cache ob_partition ob_table ob_plan_cache ob_waitevent ob_system_event ob_tenant_task ob_clog ob_memstore ob_compaction ob_unit_config ob_tenant_unit ob_system_event_detail ob_latch ob_tenant ob_tenant_server ob_tenant_server_available] metrics:map[] Tags:map[] TagNames:[ob_tenant_id] RemoveNotMatchedTagValueMessage:true}]} {QueryDataConfigs:[{QuerySQL:SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META' QueryArgs:[] MinOBVersion:4.0.0.0 MaxOBVersion:}] CacheExpire:3m0s Conditions:[{Metrics:[ob_cache ob_partition ob_table ob_plan_cache ob_waitevent ob_system_event ob_tenant_task ob_clog ob_memstore ob_compaction ob_unit_config ob_tenant_unit ob_system_event_detail ob_latch] metrics:map[] Tags:map[] TagNames:[ob_tenant_id] RemoveNotMatchedTagValueMessage:true}]} {QueryDataConfigs:[{QuerySQL:SELECT tenant_id ob_tenant_id, tenant_name FROM __all_tenant QueryArgs:[] MinOBVersion: MaxOBVersion:4.0.0.0}] CacheExpire:3m0s Conditions:[{Metrics:[ob_sysstat] metrics:map[] Tags:map[] TagNames:[ob_tenant_id] RemoveNotMatchedTagValueMessage:false}]} {QueryDataConfigs:[{QuerySQL:SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META' QueryArgs:[] MinOBVersion:4.0.0.0 MaxOBVersion:}] CacheExpire:3m0s Conditions:[{Metrics:[ob_sysstat] metrics:map[] Tags:map[] TagNames:[ob_tenant_id] RemoveNotMatchedTagValueMessage:false}]}]} 2023-04-29T13:15:52.78248+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_partition updated firstly! 2023-04-29T13:15:52.78269+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_query_response_time_seconds updated firstly! 2023-04-29T13:15:52.78281+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_trans updated firstly! 2023-04-29T13:15:52.78363+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_disk updated firstly! 2023-04-29T13:15:52.78379+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_system_event updated firstly! 2023-04-29T13:15:52.78383+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_zone updated firstly! 2023-04-29T13:15:52.78389+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for jointable-1 updated firstly! 2023-04-29T13:15:52.78393+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_role updated firstly! 2023-04-29T13:15:52.78399+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for jointable-3 updated firstly! 2023-04-29T13:15:52.78435+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_tenant_assigned updated firstly! 2023-04-29T13:15:52.78554+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:68:init: successfully init mysqlTableInput plugin 2023-04-29T13:15:52.78557+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:90:init: init exporter instance prometheusExporter 2023-04-29T13:15:52.78568+08:00 INFO [359133,d8742349c0f00883] caller=prometheus/prometheus.go:78:Init: prometheus exporter config: &{FormatType:fmtText ExposeUrl: WithTimestamp:false} 2023-04-29T13:15:52.78571+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields:, module=monitor.ob, eventType=add, duration=135.16532ms 2023-04-29T13:15:52.78575+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for jointable-0 updated firstly! 2023-04-29T13:15:52.78583+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for jointable-2 updated firstly! 2023-04-29T13:15:52.78593+08:00 INFO [359133,d8742349c0f00883] caller=monagent/monagent_route.go:77:RegisterPipelineRoute: register route /metrics/ob/basic 2023-04-29T13:15:52.78598+08:00 INFO [359133,d8742349c0f00883] caller=monagent/monagent_route.go:77:RegisterPipelineRoute: register route /metrics/ob/basic 2023-04-29T13:15:52.78605+08:00 INFO [359133,d8742349c0f00883] caller=monagent/monagent_route.go:77:RegisterPipelineRoute: register route /metrics/ob/extra 2023-04-29T13:15:52.78608+08:00 INFO [359133,d8742349c0f00883] caller=monagent/monagent_route.go:77:RegisterPipelineRoute: register route /metrics/ob/extra 2023-04-29T13:15:52.78609+08:00 INFO [359133,d8742349c0f00883] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields: duration=135.586426ms, module=monitor.ob 2023-04-29T13:15:52.78612+08:00 INFO [359133,d8742349c0f00883] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields: module=monitor.ob, eventType=add, duration=135.635227ms 2023-04-29T13:15:52.78614+08:00 INFO [359133,d8742349c0f00883] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields:, module=log.alarm, eventType=add, duration="5.6µs" 2023-04-29T13:15:52.78648+08:00 INFO [359133,] caller=inputs/all.go:60:func7: configData: {Timeout:1m0s PluginInnerConfig:map[recoveryConfig:map[enabled:true triggerThreshold:10000] tailConfigs:[map[logAnalyzerType:host_light logDir:/var/log logFileName:kern logSourceType:kern processLogInterval:500ms] map[logAnalyzerType:agent_light logDir:/home/oceanbase/fund/obagent/log logFileName:monagent.log logSourceType:monagent_log processLogInterval:500ms] map[logAnalyzerType:agent_light logDir:/home/oceanbase/fund/obagent/log logFileName:mgragent.log logSourceType:mgragent_log processLogInterval:500ms] map[logAnalyzerType:ob logDir:/home/oceanbase/fund/oceanbase/log logFileName:rootservice.log.wf logSourceType:rootservice processLogInterval:500ms] map[logAnalyzerType:ob logDir:/home/oceanbase/fund/oceanbase/log logFileName:election.log.wf logSourceType:election processLogInterval:500ms] map[logAnalyzerType:ob logDir:/home/oceanbase/fund/oceanbase/log logFileName:observer.log.wf logSourceType:observer processLogInterval:500ms]]]} 2023-04-29T13:15:52.78683+08:00 INFO [359133,] caller=inputs/all.go:71:func7: logTailerInput config: {TailConfigs:[{LogDir:/var/log LogFileName:kern ProcessLogInterval:500ms LogSourceType:kern LogAnalyzerType:host_light} {LogDir:/home/oceanbase/fund/obagent/log LogFileName:monagent.log ProcessLogInterval:500ms LogSourceType:monagent_log LogAnalyzerType:agent_light} {LogDir:/home/oceanbase/fund/obagent/log LogFileName:mgragent.log ProcessLogInterval:500ms LogSourceType:mgragent_log LogAnalyzerType:agent_light} {LogDir:/home/oceanbase/fund/oceanbase/log LogFileName:rootservice.log.wf ProcessLogInterval:500ms LogSourceType:rootservice LogAnalyzerType:ob} {LogDir:/home/oceanbase/fund/oceanbase/log LogFileName:election.log.wf ProcessLogInterval:500ms LogSourceType:election LogAnalyzerType:ob} {LogDir:/home/oceanbase/fund/oceanbase/log LogFileName:observer.log.wf ProcessLogInterval:500ms LogSourceType:observer LogAnalyzerType:ob}] RecoveryConfig:{Enabled:true LastPositionStoreDir: TriggerStoreThreshold:10000} ProcessQueueCapacity:0} 2023-04-29T13:15:52.78696+08:00 INFO [359133,] caller=retag/retag.go:63:Init: init retagProcessor with config: &{RenameTags:map[] CopyTags:map[] NewTags:map[alarmType:ob_log_alarm ip:10.0.10.102 obClusterId:1 obClusterName:fund]} 2023-04-29T13:15:52.78706+08:00 INFO [359133,] caller=outputs/all.go:52:func6: configData: map[alarmTimeWindow:3m keywordAlarmRules: logAlarmFilters:[] logFilterRulesJsonContent: logSourceType2AlarmType:map[election:election_log_alarm kern:message_log_alarm mgragent_log:mgragent_log_alarm monagent_log:monagent_log_alarm obproxy_error:obproxy_log_alarm observer:observer_log_alarm rootservice:rootservice_log_alarm]] 2023-04-29T13:15:52.78718+08:00 INFO [359133,] caller=outputs/all.go:63:func6: alarmsCacheOutput config: &{LogFilterRulesJsonContent: LogAlarmFilters:[] AlarmTimeWindow:3m0s LogSourceType2AlarmType:map[election:election_log_alarm kern:message_log_alarm mgragent_log:mgragent_log_alarm monagent_log:monagent_log_alarm obproxy_error:obproxy_log_alarm observer:observer_log_alarm rootservice:rootservice_log_alarm]} 2023-04-29T13:15:52.78722+08:00 INFO [359133,d8742349c0f00883] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields:, module=log.alarm, duration=1.062715ms 2023-04-29T13:15:52.78776+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_module_callback.go:38:addPipeline: add pipeline module config result status: succeed, description: fields:, module=monitor.ob, duration=183.464806ms 2023-04-29T13:15:52.78781+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_module_callback.go:126:func1: add pipeline module config monitor.ob successfully. 2023-04-29T13:15:52.78783+08:00 INFO [359133,] caller=monagent/monagent_route.go:77:RegisterPipelineRoute: register route /api/v1/log/alarms 2023-04-29T13:15:52.78785+08:00 INFO [359133,] caller=monagent/monagent_route.go:77:RegisterPipelineRoute: register route /api/v1/log/alarms 2023-04-29T13:15:52.78787+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields: duration="4.4µs", module=log.alarm, eventType=add 2023-04-29T13:15:52.7879+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_manager.go:211:func3: start pipelineV2 log_tailer_to_alarm 2023-04-29T13:15:52.78794+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields:, eventType=add, module=log.alarm, duration="65.2µs" 2023-04-29T13:15:52.78801+08:00 INFO [359133,] caller=log_tailer/log_tailer.go:48:Start: start to run log tailer 2023-04-29T13:15:52.78807+08:00 ERROR [359133,] caller=log_tailer/log_tailer.go:77:Run: loadLastPosition failed fields:, tailConf="{/var/log kern 500ms kern host_light}", error="invalid argument" 2023-04-29T13:15:52.78809+08:00 INFO [359133,] caller=log_tailer/log_tailer.go:77:Run: build fileProcessQueueMap with initLogQueue fields: tailConf="{/var/log kern 500ms kern host_light}", initLogQueue="[]" 2023-04-29T13:15:52.78812+08:00 ERROR [359133,] caller=log_tailer/log_tailer.go:77:Run: loadLastPosition failed fields:, tailConf="{/home/oceanbase/fund/obagent/log monagent.log 500ms monagent_log agent_light}", error="invalid argument" 2023-04-29T13:15:52.78813+08:00 INFO [359133,] caller=log_tailer/log_tailer.go:77:Run: build fileProcessQueueMap with initLogQueue fields:, tailConf="{/home/oceanbase/fund/obagent/log monagent.log 500ms monagent_log agent_light}", initLogQueue="[]" 2023-04-29T13:15:52.78816+08:00 ERROR [359133,] caller=log_tailer/log_tailer.go:77:Run: loadLastPosition failed fields: tailConf="{/home/oceanbase/fund/obagent/log mgragent.log 500ms mgragent_log agent_light}", error="invalid argument" 2023-04-29T13:15:52.78817+08:00 INFO [359133,] caller=log_tailer/log_tailer.go:77:Run: build fileProcessQueueMap with initLogQueue fields:, tailConf="{/home/oceanbase/fund/obagent/log mgragent.log 500ms mgragent_log agent_light}", initLogQueue="[]" 2023-04-29T13:15:52.7882+08:00 ERROR [359133,] caller=log_tailer/log_tailer.go:77:Run: loadLastPosition failed fields:, tailConf="{/home/oceanbase/fund/oceanbase/log rootservice.log.wf 500ms rootservice ob}", error="invalid argument" 2023-04-29T13:15:52.78822+08:00 INFO [359133,] caller=log_tailer/log_tailer.go:77:Run: build fileProcessQueueMap with initLogQueue fields:, tailConf="{/home/oceanbase/fund/oceanbase/log rootservice.log.wf 500ms rootservice ob}", initLogQueue="[]" 2023-04-29T13:15:52.78824+08:00 ERROR [359133,] caller=log_tailer/log_tailer.go:77:Run: loadLastPosition failed fields:, tailConf="{/home/oceanbase/fund/oceanbase/log election.log.wf 500ms election ob}", error="invalid argument" 2023-04-29T13:15:52.78826+08:00 INFO [359133,] caller=log_tailer/log_tailer.go:77:Run: build fileProcessQueueMap with initLogQueue fields:, tailConf="{/home/oceanbase/fund/oceanbase/log election.log.wf 500ms election ob}", initLogQueue="[]" 2023-04-29T13:15:52.78828+08:00 ERROR [359133,] caller=log_tailer/log_tailer.go:77:Run: loadLastPosition failed fields: tailConf="{/home/oceanbase/fund/oceanbase/log observer.log.wf 500ms observer ob}", error="invalid argument" 2023-04-29T13:15:52.7883+08:00 INFO [359133,] caller=log_tailer/log_tailer.go:77:Run: build fileProcessQueueMap with initLogQueue fields: initLogQueue="[]", tailConf="{/home/oceanbase/fund/oceanbase/log observer.log.wf 500ms observer ob}" 2023-04-29T13:15:52.78833+08:00 INFO [359133,] caller=log_tailer/log_tailer_executor.go:193:WatchFile: start watching fields: fileRealPath=/home/oceanbase/fund/oceanbase/log/observer.log.wf 2023-04-29T13:15:52.78835+08:00 INFO [359133,d8742349c0f00883] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields:, module=log.alarm, duration=2.189731ms 2023-04-29T13:15:52.78836+08:00 INFO [359133,d8742349c0f00883] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields:, module=log.alarm, eventType=add, duration=2.227031ms 2023-04-29T13:15:52.78839+08:00 INFO [359133,d8742349c0f00883] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields:, module=node.custom, eventType=add, duration="5.6µs" 2023-04-29T13:15:52.78841+08:00 INFO [359133,d8742349c0f00883] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields:, module=node.custom, duration="3.9µs" 2023-04-29T13:15:52.78843+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields: module=node.custom, duration="3.901µs", eventType=add 2023-04-29T13:15:52.78845+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:48:init: init input instance hostCustomInput 2023-04-29T13:15:52.78909+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:48:init: init input instance processInput 2023-04-29T13:15:52.7892+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:62:init: init processor instance attrProcessor 2023-04-29T13:15:52.78947+08:00 INFO [359133,d8742349c0f00883] caller=attr/attribute_operate.go:61:Init: init retagProcessor with config: {Operations:[{Oper:copyTags Condition:{Metric: Fields:map[] Tags:map[]} Tags:map[dev:device] RemoveItems:[]} {Oper:addTags Condition:{Metric: Fields:map[] Tags:map[]} Tags:map[app:HOST ob_cluster_id:1 ob_cluster_name:fund obproxy_cluster: obproxy_cluster_id:0 obzone:zone1 svr_ip:10.0.10.102] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:observer_coredump_time_seconds Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:observer_ulimit_max_fd_count Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:observer_fd_count Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:ob_log_disk_writable Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:ob_data_disk_writable Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]}]} 2023-04-29T13:15:52.7895+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:62:init: init processor instance mountLabelProcessor 2023-04-29T13:15:52.7896+08:00 INFO [359133,d8742349c0f00883] caller=label/mount_label.go:70:Init: init mountLabelProcessor with config: &{LabelTags:map[dataDiskPath:/home/oceanbase/fund/oceanbase/store logDiskPath:/home/oceanbase/fund/oceanbase/store] ObStatus:active} 2023-04-29T13:15:52.79724+08:00 INFO [359133,] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=df ., timeout=10s}, exitCode=1 fields:, duration=7.587208ms 2023-04-29T13:15:52.7973+08:00 WARN [359133,] caller=common/mount.go:22:GetMountPath: get path's mount failed, filePath: . 2023-04-29T13:15:52.80422+08:00 INFO [359133,] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=df /data/fund, timeout=10s}, exitCode=1 fields: duration=6.894498ms 2023-04-29T13:15:52.80427+08:00 WARN [359133,] caller=common/mount.go:22:GetMountPath: get path's mount failed, filePath: /data/fund 2023-04-29T13:15:52.80736+08:00 INFO [359133,] caller=log_tailer/log_tailer_executor.go:193:WatchFile: start watching fields:, fileRealPath=/var/log/kern 2023-04-29T13:15:52.80744+08:00 INFO [359133,] caller=log_tailer/log_tailer_executor.go:193:WatchFile: start watching fields:, fileRealPath=/home/oceanbase/fund/obagent/log/monagent.log 2023-04-29T13:15:52.80747+08:00 INFO [359133,] caller=log_tailer/log_tailer_executor.go:193:WatchFile: start watching fields: fileRealPath=/home/oceanbase/fund/obagent/log/mgragent.log 2023-04-29T13:15:52.80755+08:00 INFO [359133,] caller=log_tailer/log_tailer_executor.go:193:WatchFile: start watching fields:, fileRealPath=/home/oceanbase/fund/oceanbase/log/rootservice.log.wf 2023-04-29T13:15:52.8076+08:00 INFO [359133,] caller=log_tailer/log_tailer_executor.go:193:WatchFile: start watching fields: fileRealPath=/home/oceanbase/fund/oceanbase/log/election.log.wf 2023-04-29T13:15:52.80763+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_module_callback.go:38:addPipeline: add pipeline module config result status: succeed, description: fields:, module=log.alarm, duration=157.829942ms 2023-04-29T13:15:52.80766+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_module_callback.go:126:func1: add pipeline module config log.alarm successfully. 2023-04-29T13:15:52.80913+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for process updated firstly! 2023-04-29T13:15:52.80928+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for jointable-1 updated firstly! 2023-04-29T13:15:52.80932+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_unit updated firstly! 2023-04-29T13:15:52.80944+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_unit_config updated firstly! 2023-04-29T13:15:52.80957+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_tenant_resource updated firstly! 2023-04-29T13:15:52.8097+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_tenant_disk updated firstly! 2023-04-29T13:15:52.80977+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_tenant500_memory updated firstly! 2023-04-29T13:15:52.80985+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_memstore updated firstly! 2023-04-29T13:15:52.81001+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for io_infos updated firstly! 2023-04-29T13:15:52.81145+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for cpu_count updated firstly! 2023-04-29T13:15:52.81184+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for jointable-3 updated firstly! 2023-04-29T13:15:52.8124+08:00 INFO [359133,] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=df /data/fund, timeout=10s}, exitCode=1 fields:, duration=8.112315ms 2023-04-29T13:15:52.81245+08:00 WARN [359133,] caller=common/mount.go:22:GetMountPath: get path's mount failed, filePath: /data/fund 2023-04-29T13:15:52.81247+08:00 WARN [359133,] caller=common/mount.go:15:GetMountPath: check filepath stat failed, err: stat : no such file or directory 2023-04-29T13:15:52.81574+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=ethtool lo, timeout=50s}, exitCode=1 fields:, duration=7.180802ms 2023-04-29T13:15:52.8158+08:00 WARN [359133,d8742349c0f00883] caller=host/custom.go:475:doCollectBandwidthInfo: get bandwidth of net interface lo failed, cmd: ethtool lo 2023-04-29T13:15:52.81677+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.861226ms 2023-04-29T13:15:52.81684+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:15:52.81687+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for node_ntp_offset_seconds updated firstly! 2023-04-29T13:15:52.8198+08:00 INFO [359133,] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=df -h, timeout=10s}, exitCode=1 fields: duration=7.276203ms 2023-04-29T13:15:52.81992+08:00 WARN [359133,d8742349c0f00883] caller=label/mount_label.go:187:getMountPV: execute cmd df -h failed, err: failed to execute command: Command{user=admin, program=sh, outputType=combined, cmd=df -h, timeout=10s}, exitCode: 1, output: 2023-04-29T13:15:52.81994+08:00 WARN [359133,d8742349c0f00883] caller=engine/plugin_instance.go:68:init: get mountPV failed 2023-04-29T13:15:52.81996+08:00 INFO [359133,d8742349c0f00883] caller=engine/plugin_instance.go:90:init: init exporter instance prometheusExporter 2023-04-29T13:15:52.8201+08:00 INFO [359133,d8742349c0f00883] caller=prometheus/prometheus.go:78:Init: prometheus exporter config: &{FormatType:fmtText ExposeUrl: WithTimestamp:false} 2023-04-29T13:15:52.82012+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields:, module=node.custom, eventType=add, duration=31.695351ms 2023-04-29T13:15:52.82015+08:00 INFO [359133,d8742349c0f00883] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields: duration=31.745651ms, module=node.custom 2023-04-29T13:15:52.82017+08:00 INFO [359133,d8742349c0f00883] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields: duration=31.781451ms, module=node.custom, eventType=add 2023-04-29T13:15:52.82018+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_module_callback.go:38:addPipeline: add pipeline module config result status: succeed, description: fields:, module=node.custom, duration=170.31502ms 2023-04-29T13:15:52.82026+08:00 INFO [359133,d8742349c0f00883] caller=engine/pipeline_module_callback.go:126:func1: add pipeline module config node.custom successfully. 2023-04-29T13:15:52.82319+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=ethtool eth0, timeout=50s}, exitCode=1 fields: duration=7.370904ms 2023-04-29T13:15:52.82323+08:00 WARN [359133,d8742349c0f00883] caller=host/custom.go:475:doCollectBandwidthInfo: get bandwidth of net interface eth0 failed, cmd: ethtool eth0 2023-04-29T13:15:52.82325+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for bandwidth_infos updated firstly! 2023-04-29T13:15:52.82796+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_table updated firstly! 2023-04-29T13:15:52.85747+08:00 INFO [359133,] caller=common/input_cache.go:30:Update: cache for ob_index updated firstly! 2023-04-29T13:15:53.28861+08:00 INFO [359133,] caller=log_tailer/log_tailer_executor.go:227:WatchFile: add logFileInfo to empty queue fields:, fileRealPath=/home/oceanbase/fund/oceanbase/log/observer.log.wf 2023-04-29T13:15:53.30783+08:00 INFO [359133,] caller=log_tailer/log_tailer_executor.go:227:WatchFile: add logFileInfo to empty queue fields:, fileRealPath=/home/oceanbase/fund/obagent/log/monagent.log 2023-04-29T13:15:53.30792+08:00 INFO [359133,] caller=log_tailer/log_tailer_executor.go:227:WatchFile: add logFileInfo to empty queue fields:, fileRealPath=/home/oceanbase/fund/obagent/log/mgragent.log 2023-04-29T13:15:53.30798+08:00 INFO [359133,] caller=log_tailer/log_tailer_executor.go:227:WatchFile: add logFileInfo to empty queue fields:, fileRealPath=/home/oceanbase/fund/oceanbase/log/rootservice.log.wf 2023-04-29T13:15:53.30803+08:00 INFO [359133,] caller=log_tailer/log_tailer_executor.go:227:WatchFile: add logFileInfo to empty queue fields:, fileRealPath=/home/oceanbase/fund/oceanbase/log/election.log.wf 2023-04-29T13:15:53.48299+08:00 INFO [359133,] caller=shell/exec.go:88:execute: execute shell command start, command=Command{user=oceanbase, program=sh, outputType=std, cmd=netstat -tunlp 2>/dev/null | { grep '359133/' || true; }, timeout=10s} fields:, duration="29.9µs" 2023-04-29T13:15:53.49732+08:00 INFO [359133,] caller=shell/exec.go:127:execute: execute shell command end, command=Command{user=oceanbase, program=sh, outputType=std, cmd=netstat -tunlp 2>/dev/null | { grep '359133/' || true; }, timeout=10s} fields:, duration=14.367004ms 2023-04-29T13:15:57.72789+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.636023ms 2023-04-29T13:15:57.72798+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:15:57.82521+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.263118ms 2023-04-29T13:15:57.82528+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:15:59.6743+08:00 INFO [359133,] caller=shell/exec.go:88:execute: execute shell command start, command=Command{user=oceanbase, program=sh, outputType=std, cmd=netstat -tunlp 2>/dev/null | { grep '359133/' || true; }, timeout=10s} fields:, duration="37.7µs" 2023-04-29T13:15:59.69212+08:00 INFO [359133,] caller=shell/exec.go:127:execute: execute shell command end, command=Command{user=oceanbase, program=sh, outputType=std, cmd=netstat -tunlp 2>/dev/null | { grep '359133/' || true; }, timeout=10s} fields:, duration=17.862953ms 2023-04-29T13:15:59.77084+08:00 INFO [359133,] caller=shell/exec.go:88:execute: execute shell command start, command=Command{user=oceanbase, program=sh, outputType=std, cmd=netstat -tunlp 2>/dev/null | { grep '359133/' || true; }, timeout=10s} fields:, duration="29.901µs" 2023-04-29T13:15:59.78532+08:00 INFO [359133,] caller=shell/exec.go:127:execute: execute shell command end, command=Command{user=oceanbase, program=sh, outputType=std, cmd=netstat -tunlp 2>/dev/null | { grep '359133/' || true; }, timeout=10s} fields:, duration=14.508206ms 2023-04-29T13:16:02.72769+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.337319ms 2023-04-29T13:16:02.72776+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:16:02.82698+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.526835ms 2023-04-29T13:16:02.82705+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:16:07.72745+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.258817ms 2023-04-29T13:16:07.72753+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:16:07.82625+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.415105ms 2023-04-29T13:16:07.82633+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:16:12.72679+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.981114ms 2023-04-29T13:16:12.72687+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:16:12.82769+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.262146ms 2023-04-29T13:16:12.82779+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:16:17.7274+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.489021ms 2023-04-29T13:16:17.72747+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:16:17.82511+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.005614ms 2023-04-29T13:16:17.82518+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:16:22.73043+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.007356ms 2023-04-29T13:16:22.7305+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:16:22.82535+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.928512ms 2023-04-29T13:16:22.82545+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:16:27.72913+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.704652ms 2023-04-29T13:16:27.72921+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:16:27.8256+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.962613ms 2023-04-29T13:16:27.82572+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:16:32.7284+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.207531ms 2023-04-29T13:16:32.72847+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:16:32.82595+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.40542ms 2023-04-29T13:16:32.82609+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:16:37.72675+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.119315ms 2023-04-29T13:16:37.72682+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:16:37.82523+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.641608ms 2023-04-29T13:16:37.82531+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:16:42.72708+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.873112ms 2023-04-29T13:16:42.72715+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:16:42.82551+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.71281ms 2023-04-29T13:16:42.82557+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:16:45.47079+08:00 INFO [359133,afae59b37aef0817] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=afae59b37aef0817, body=] 2023-04-29T13:16:45.47148+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:16:45.47152+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:16:45.47658+08:00 INFO [359133,9e2de581f1ebbbe3] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=9e2de581f1ebbbe3, body=] 2023-04-29T13:16:45.47675+08:00 INFO [359133,ee79ad901f0edbb5] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=ee79ad901f0edbb5, body=] 2023-04-29T13:16:45.47759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47765+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47768+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47769+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.4777+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47772+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47777+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47784+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47786+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.4779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.478+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47807+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.4781+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47811+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47816+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47817+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47827+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47828+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47835+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47837+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47839+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47841+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47848+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47849+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.4785+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47852+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47853+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47856+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47857+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47861+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47862+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47864+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47865+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47866+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47868+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47869+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.4787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47872+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47873+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47875+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47877+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47878+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.4788+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47881+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47882+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47883+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47885+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47886+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47887+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47889+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.4789+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47891+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47893+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47894+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47895+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47896+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47898+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47899+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.479+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47902+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47903+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47904+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47905+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47907+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47908+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47909+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47911+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47912+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47913+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47914+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47916+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.47917+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.47918+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.4801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.48014+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.48016+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.48018+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.48023+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.48025+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.48026+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.48027+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.48029+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.4803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.48031+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.48033+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.48035+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.48036+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.48039+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.4804+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.48042+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.48043+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.48045+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.48046+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.48047+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.48049+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.4805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.48051+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.48052+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.48054+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.48055+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.48057+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.48058+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.48116+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:45.48118+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:16:45.48119+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:16:47.72747+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.377419ms 2023-04-29T13:16:47.72753+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:16:47.82548+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.537407ms 2023-04-29T13:16:47.82555+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:16:52.76014+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=28.791209ms 2023-04-29T13:16:52.7602+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:16:52.8249+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.627308ms 2023-04-29T13:16:52.82496+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:16:57.72604+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.623809ms 2023-04-29T13:16:57.7261+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:16:57.82515+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.639808ms 2023-04-29T13:16:57.82521+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:00.24083+08:00 INFO [359133,1caf6ce2290aa618] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=1caf6ce2290aa618, body=] 2023-04-29T13:17:00.24176+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.2418+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24182+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24183+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24185+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24186+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24188+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.2419+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24191+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24196+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24198+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.242+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24201+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24202+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24204+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24206+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24207+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24208+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.2421+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24211+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24212+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24214+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24215+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24216+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24218+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24219+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.2422+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24222+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24223+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24224+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24226+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24227+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24228+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.2423+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24231+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24232+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24233+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24235+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24236+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24241+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24242+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24243+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24245+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24246+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24248+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24249+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.2425+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24252+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24253+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24255+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24256+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24257+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24259+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.2426+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24261+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24263+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24264+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24266+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24267+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24268+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24269+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24271+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24272+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24274+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24275+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24276+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24278+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24279+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.2428+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24282+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24283+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24284+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24286+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24287+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24288+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.2429+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24294+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24296+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24297+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24299+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.243+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24302+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24304+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24305+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24306+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24308+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24309+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.2431+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24312+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24313+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24314+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24316+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24317+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24318+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.2432+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24321+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24322+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24323+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24325+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24326+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24327+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.2438+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24388+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.2439+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24391+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24392+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24394+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24395+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24397+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24402+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24403+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24405+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24406+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24407+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24409+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.2441+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24411+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24412+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24414+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24415+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24416+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24417+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24419+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.2442+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.24421+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:00.24423+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:00.2453+08:00 INFO [359133,dfa17176289fbc1b] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=dfa17176289fbc1b, body=] 2023-04-29T13:17:00.24589+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:17:00.24597+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:17:00.25044+08:00 INFO [359133,3115b9da41a94473] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=3115b9da41a94473, body=] 2023-04-29T13:17:02.72589+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.131401ms 2023-04-29T13:17:02.72595+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:02.82546+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.997614ms 2023-04-29T13:17:02.82553+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:07.72695+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.662308ms 2023-04-29T13:17:07.72702+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:07.82475+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.807411ms 2023-04-29T13:17:07.82481+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:12.72632+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.465306ms 2023-04-29T13:17:12.7264+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:12.82525+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.481007ms 2023-04-29T13:17:12.82531+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:15.23773+08:00 INFO [359133,552659e2658d35c9] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=552659e2658d35c9, body=] 2023-04-29T13:17:15.23869+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23873+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23875+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23876+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23878+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23879+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23881+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23882+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23883+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23884+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23886+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23888+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23889+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.2389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23892+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23893+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23894+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23896+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23898+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23899+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.239+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23902+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23903+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23904+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23906+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23907+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23908+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.2391+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23911+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23912+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23913+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23915+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23916+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23917+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23918+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.2392+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23921+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23922+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23928+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23929+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.2393+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23932+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23937+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.2394+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23942+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23944+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23945+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23946+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23948+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23949+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.2395+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23952+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23953+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23954+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23956+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23957+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23958+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23959+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23961+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23962+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23964+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23965+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23966+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23968+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23969+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.2397+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23971+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23973+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23974+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23975+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23977+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23978+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.2398+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23981+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23982+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23983+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.2399+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23991+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23993+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23994+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23996+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.23997+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.23998+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24001+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24002+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24004+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24005+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24006+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24007+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24009+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.2401+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24011+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24013+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24014+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24015+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24016+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24018+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24019+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.2402+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24021+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24023+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24075+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24078+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.2408+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24081+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24084+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24085+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24086+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24088+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24089+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24091+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24092+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24094+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24095+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24096+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24098+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24099+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.241+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24102+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24103+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24104+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24106+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24107+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24108+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24109+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24111+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24112+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24113+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24114+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24116+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24117+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24118+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:15.24119+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:15.24241+08:00 INFO [359133,7e78e3c4df788ee6] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=7e78e3c4df788ee6, body=] 2023-04-29T13:17:15.24254+08:00 INFO [359133,a2e6a9b762f50f8b] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=a2e6a9b762f50f8b, body=] 2023-04-29T13:17:15.24328+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:17:15.24331+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:17:17.72674+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.626408ms 2023-04-29T13:17:17.7268+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:17.82462+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.398506ms 2023-04-29T13:17:17.82468+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:22.72806+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.206731ms 2023-04-29T13:17:22.72814+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:22.8246+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.285903ms 2023-04-29T13:17:22.82466+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:27.72564+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.950298ms 2023-04-29T13:17:27.72571+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:27.82439+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.248503ms 2023-04-29T13:17:27.82446+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:30.23649+08:00 INFO [359133,8cc261b3d4a5e517] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=8cc261b3d4a5e517, body=] 2023-04-29T13:17:30.23743+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23749+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.2375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23752+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23753+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23756+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23766+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23767+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23768+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.2377+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23771+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23772+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23775+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23776+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23777+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23779+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.2378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23786+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23793+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23797+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23801+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23816+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23817+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23829+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.2383+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23831+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23833+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23834+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23835+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23837+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.2384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23841+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23853+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23862+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23863+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23864+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23871+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23873+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23874+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23875+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23877+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23878+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23879+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23882+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23883+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23885+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23886+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23887+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23888+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.2389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23891+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23892+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23894+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23895+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23896+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23898+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23899+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23952+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23955+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23962+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23963+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23965+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23966+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23968+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23969+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23971+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23972+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23973+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23975+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23976+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23977+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23979+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.2398+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23981+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23982+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23984+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23985+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23986+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23988+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23989+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.2399+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23993+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23995+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23996+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.23997+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.23999+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.24+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.24001+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:30.24003+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:30.24116+08:00 INFO [359133,6365e28974821aac] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=6365e28974821aac, body=] 2023-04-29T13:17:30.24129+08:00 INFO [359133,ae61c3ff98c19444] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=ae61c3ff98c19444, body=] 2023-04-29T13:17:30.24214+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:17:30.24218+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:17:32.72717+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.056414ms 2023-04-29T13:17:32.72728+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:32.82572+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.003714ms 2023-04-29T13:17:32.8258+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:37.72699+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.864011ms 2023-04-29T13:17:37.72708+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:37.82452+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.553708ms 2023-04-29T13:17:37.82459+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:42.72598+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.571208ms 2023-04-29T13:17:42.72604+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:42.82491+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.446206ms 2023-04-29T13:17:42.82498+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:45.2369+08:00 INFO [359133,de763508064d45a2] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=de763508064d45a2, body=] 2023-04-29T13:17:45.238+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23804+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23812+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23813+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23823+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.2384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23841+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.2385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.2386+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23866+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23868+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23871+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23874+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23877+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23879+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23881+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23883+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23885+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23886+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23887+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23889+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.2389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23891+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23893+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23894+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23895+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23897+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23898+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23899+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23902+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23903+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23904+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23905+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23907+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23909+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.2391+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23912+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23914+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23916+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23919+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23921+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23923+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23924+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23925+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23927+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23928+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23929+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.2393+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23932+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23934+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23935+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23936+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23939+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23941+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23943+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23944+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23945+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23946+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23948+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23949+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.2395+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23951+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23953+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23954+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23955+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23956+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23958+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23959+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.2396+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23961+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23963+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23964+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23965+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23967+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23968+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23969+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23971+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23972+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23973+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.23974+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.23976+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.24037+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.24042+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.24044+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.24045+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.24047+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.24048+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.24049+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.24051+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.24052+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.24053+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.24055+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.24056+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.24058+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.24059+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.2406+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.24062+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.24063+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.24065+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.24066+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.24067+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.24069+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.2407+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.24071+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.24073+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.24074+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.24075+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.24077+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.24078+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.24079+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.24081+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.24082+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:17:45.24083+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:17:45.24204+08:00 INFO [359133,e16ffac9869ac9ee] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=e16ffac9869ac9ee, body=] 2023-04-29T13:17:45.24218+08:00 INFO [359133,81af0c2cbdff564d] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=81af0c2cbdff564d, body=] 2023-04-29T13:17:45.2429+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:17:45.24293+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:17:47.72605+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.069501ms 2023-04-29T13:17:47.72611+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:47.8252+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.597808ms 2023-04-29T13:17:47.82527+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:52.75313+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=23.075828ms 2023-04-29T13:17:52.75319+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:52.82474+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.296603ms 2023-04-29T13:17:52.82484+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:57.72704+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.74681ms 2023-04-29T13:17:57.72711+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:17:57.82477+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.316504ms 2023-04-29T13:17:57.82483+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:00.2361+08:00 INFO [359133,edf1029c162ec266] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=edf1029c162ec266, body=] 2023-04-29T13:18:00.23704+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23708+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23715+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23718+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23719+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.2372+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23722+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23723+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23724+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23727+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23728+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23732+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23733+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23736+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23738+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.2374+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23741+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23743+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23744+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23745+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23746+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23748+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23749+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.2375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23752+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.2376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23761+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23762+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23765+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23769+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23777+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23781+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23787+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23788+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23791+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23792+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23793+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23795+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23796+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23798+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23802+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23812+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23815+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23816+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23819+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.2382+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23821+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23823+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23824+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23825+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23826+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23828+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23829+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23832+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23833+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23839+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.2384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23846+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.2385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23915+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23918+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.2392+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23921+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23923+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23924+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23925+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23926+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23928+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23929+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.2393+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23937+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23941+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23942+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23944+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23945+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23947+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23956+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23959+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.2396+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23961+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23962+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23964+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23965+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23966+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23968+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23969+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.2397+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23971+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23973+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.23975+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:00.23976+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:00.24105+08:00 INFO [359133,8e20f3fa8b2cbdbf] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=8e20f3fa8b2cbdbf, body=] 2023-04-29T13:18:00.24167+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:18:00.24171+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:18:00.2528+08:00 INFO [359133,4bb6295e8dcfe113] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=4bb6295e8dcfe113, body=] 2023-04-29T13:18:02.72575+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.152102ms 2023-04-29T13:18:02.72582+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:02.82508+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.851012ms 2023-04-29T13:18:02.82514+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:07.72665+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.335005ms 2023-04-29T13:18:07.72671+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:07.82462+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.312004ms 2023-04-29T13:18:07.82469+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:12.72624+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.885512ms 2023-04-29T13:18:12.72631+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:12.82503+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.313804ms 2023-04-29T13:18:12.8251+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:15.23919+08:00 INFO [359133,194a527d7d418bfc] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=194a527d7d418bfc, body=] 2023-04-29T13:18:15.24036+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.2407+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24073+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24074+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24076+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24077+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24079+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.2408+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24081+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24083+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24084+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24085+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24087+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24088+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.2409+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24091+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24092+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24094+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24095+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24096+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24098+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24099+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.241+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24102+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24103+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24104+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24106+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24107+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24109+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.2411+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24112+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24113+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24115+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24116+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24117+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24119+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.2412+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24121+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24123+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24124+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24125+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24127+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24128+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24129+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24131+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24132+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24133+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24134+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24136+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24138+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.2414+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24141+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24143+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24144+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24145+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24147+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24148+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24149+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24151+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24152+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24154+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24155+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24157+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24158+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24159+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24161+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24162+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24163+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24165+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24166+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24167+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24169+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.2417+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24171+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24173+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24174+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24175+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24177+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24178+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24179+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24181+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24182+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24183+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24185+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24186+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24188+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24189+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.2419+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24192+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24194+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24196+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24197+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24198+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.242+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24201+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24203+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24204+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24205+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24207+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24208+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24209+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24211+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24264+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24267+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24269+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.2427+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24272+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24273+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24274+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24276+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24277+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24278+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.2428+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24281+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24282+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24284+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24285+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24286+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24288+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24289+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24292+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24296+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24297+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24299+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.243+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24301+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24303+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24304+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24306+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24307+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24308+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.2431+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24311+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:15.24312+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:15.24421+08:00 INFO [359133,eeaeeb21e1713b30] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=eeaeeb21e1713b30, body=] 2023-04-29T13:18:15.24479+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:18:15.24482+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:18:15.24962+08:00 INFO [359133,9a14e87ba075ba61] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=9a14e87ba075ba61, body=] 2023-04-29T13:18:17.72774+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.686323ms 2023-04-29T13:18:17.72782+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:17.82486+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.610008ms 2023-04-29T13:18:17.82493+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:22.72667+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.589208ms 2023-04-29T13:18:22.72676+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:22.82509+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.473906ms 2023-04-29T13:18:22.82516+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:27.726+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.358205ms 2023-04-29T13:18:27.72607+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:27.82457+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.156102ms 2023-04-29T13:18:27.82463+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:30.23617+08:00 INFO [359133,a94157449f2cafc2] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=a94157449f2cafc2, body=] 2023-04-29T13:18:30.23707+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23714+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23716+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23717+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23718+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.2372+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23724+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23725+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23728+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23729+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.2373+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23732+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23733+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23734+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23737+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23739+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23741+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23744+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23747+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23748+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23752+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23756+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.2376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23762+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23769+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23776+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23777+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23779+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.2378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23783+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23787+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23788+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23791+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23792+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23794+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23795+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23796+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23798+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23799+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.238+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23802+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23803+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23804+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23806+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23807+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23811+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23816+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23817+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23829+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.2383+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23832+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23833+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23838+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.2384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23841+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23842+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23843+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23846+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23847+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.2385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23899+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23902+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23903+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23904+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23906+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23907+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23908+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.2391+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23911+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23912+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23914+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23915+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23916+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23918+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23919+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.2392+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23922+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23923+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23924+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23925+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23927+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23928+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.2393+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23931+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23932+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23934+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23935+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23936+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23939+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23953+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.23955+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:30.23957+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:30.24094+08:00 INFO [359133,ed7fe9e96b32d1d5] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=ed7fe9e96b32d1d5, body=] 2023-04-29T13:18:30.24159+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:18:30.24163+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:18:30.24593+08:00 INFO [359133,82d026c04f62249c] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=82d026c04f62249c, body=] 2023-04-29T13:18:32.72771+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.368719ms 2023-04-29T13:18:32.72778+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:32.82476+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.564708ms 2023-04-29T13:18:32.82486+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:37.72709+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.77941ms 2023-04-29T13:18:37.72718+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:37.8252+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.474806ms 2023-04-29T13:18:37.82527+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:42.7269+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.968713ms 2023-04-29T13:18:42.72696+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:42.82481+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.503006ms 2023-04-29T13:18:42.82487+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:45.23604+08:00 INFO [359133,5aaa559035a8ab68] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=5aaa559035a8ab68, body=] 2023-04-29T13:18:45.23688+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23692+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23694+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23696+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23698+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23699+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23701+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23703+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23707+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23711+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23715+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23718+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23721+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23722+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23738+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23761+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23762+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23766+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23767+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23768+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23769+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23771+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23772+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23775+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23776+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23777+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23779+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.2378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23796+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23797+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.238+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23801+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23804+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23807+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23816+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23822+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23826+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23829+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23834+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23837+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23896+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23899+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23901+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23902+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23903+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23905+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23908+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23909+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23911+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23912+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23913+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23915+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23916+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23917+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23919+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.2392+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23921+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23922+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23924+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23925+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23927+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23928+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23929+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.2393+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23932+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23933+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23935+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23936+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23939+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.2394+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.23941+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:18:45.23943+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:18:45.24061+08:00 INFO [359133,7c799b8a6310bfca] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=7c799b8a6310bfca, body=] 2023-04-29T13:18:45.24127+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:18:45.2413+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:18:45.24589+08:00 INFO [359133,5c644b3aed90ede2] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=5c644b3aed90ede2, body=] 2023-04-29T13:18:47.72654+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.308204ms 2023-04-29T13:18:47.72661+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:47.82507+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.120016ms 2023-04-29T13:18:47.82517+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:52.73835+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.530307ms 2023-04-29T13:18:52.73844+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:52.82425+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.237903ms 2023-04-29T13:18:52.82431+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:57.72804+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.973127ms 2023-04-29T13:18:57.72812+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:18:57.8258+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.332819ms 2023-04-29T13:18:57.82586+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:00.23677+08:00 INFO [359133,f839744762bd862f] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=f839744762bd862f, body=] 2023-04-29T13:19:00.23765+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23769+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23771+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23772+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23775+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23776+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23777+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23779+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.2378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23783+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23787+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23789+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.2379+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23793+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23794+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23798+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23802+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23806+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23807+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.2381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23811+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23813+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23816+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23821+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23822+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23825+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23826+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23832+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23834+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23837+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23839+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.2384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23845+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23846+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23849+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.2385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.2386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23864+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23866+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23867+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23868+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23871+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23876+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23878+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.2388+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23882+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23883+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23885+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23887+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23888+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.2389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23891+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23893+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23894+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23895+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23896+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23898+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23899+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23902+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23903+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23905+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23906+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23907+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23909+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.2391+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23911+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23969+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23973+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23981+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23983+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23984+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23986+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23987+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23988+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.2399+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23991+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23992+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23994+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23995+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.23997+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.23998+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.24+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.24001+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.24002+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.24004+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.24005+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.24006+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.24008+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.24009+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.2401+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.24012+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.24019+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.24021+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.24027+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.24029+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.2403+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.24031+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:00.24033+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:00.24145+08:00 INFO [359133,39229dfad1192b30] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=39229dfad1192b30, body=] 2023-04-29T13:19:00.24196+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:19:00.242+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:19:00.2539+08:00 INFO [359133,388c0dabeece43d6] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=388c0dabeece43d6, body=] 2023-04-29T13:19:02.7264+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.72661ms 2023-04-29T13:19:02.72647+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:02.82513+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.211102ms 2023-04-29T13:19:02.82524+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:07.72606+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.139502ms 2023-04-29T13:19:07.72613+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:07.82553+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.557608ms 2023-04-29T13:19:07.82559+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:12.72687+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.290118ms 2023-04-29T13:19:12.72694+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:12.82461+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.299704ms 2023-04-29T13:19:12.82469+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:15.23597+08:00 INFO [359133,6400f5ee757436ad] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=6400f5ee757436ad, body=] 2023-04-29T13:19:15.23706+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.2371+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23712+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23713+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23714+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23716+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23717+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23719+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.2372+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23723+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23739+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23745+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23746+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.2376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23762+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23765+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23766+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23767+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23769+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.2377+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23771+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23773+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23774+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23777+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23778+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23779+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23781+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23782+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23784+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23792+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23793+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23797+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.2381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23812+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23813+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23815+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23816+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.2382+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23821+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23823+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23824+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23827+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23829+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.2383+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23831+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23834+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23835+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23839+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23841+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23842+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23843+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23846+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23847+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.2385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.2391+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23913+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23915+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23916+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23918+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23919+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23921+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23922+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23923+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23925+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23927+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23928+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23929+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23931+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23932+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23933+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23935+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23936+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23939+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.2394+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23942+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23943+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23944+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23945+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23947+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23948+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23958+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23959+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23961+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23962+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.23963+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:15.23964+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:15.24099+08:00 INFO [359133,96234411dadda68d] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=96234411dadda68d, body=] 2023-04-29T13:19:15.24113+08:00 INFO [359133,bb95ea094664c85f] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=bb95ea094664c85f, body=] 2023-04-29T13:19:15.2418+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:19:15.24184+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:19:17.73053+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.475463ms 2023-04-29T13:19:17.7306+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:17.82628+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.396519ms 2023-04-29T13:19:17.82635+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:22.72581+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.961099ms 2023-04-29T13:19:22.72587+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:22.82551+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.553907ms 2023-04-29T13:19:22.82557+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:27.72742+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.633523ms 2023-04-29T13:19:27.72749+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:27.82544+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.497807ms 2023-04-29T13:19:27.82551+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:30.23564+08:00 INFO [359133,425c2ac79e6648a2] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=425c2ac79e6648a2, body=] 2023-04-29T13:19:30.2365+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23654+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23656+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23657+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23659+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.2366+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23662+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23664+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23665+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23666+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23668+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23669+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23671+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23672+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23673+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23674+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23676+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23677+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23678+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.2368+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23681+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23682+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23684+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23685+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23686+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23688+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23689+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.2369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23692+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23693+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23694+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23697+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23698+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23705+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23707+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23711+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23718+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23727+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.2373+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23739+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23741+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23745+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23746+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23748+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23749+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.2375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23752+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23753+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23754+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23756+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23757+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23758+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.2376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23761+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23762+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23765+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23778+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23783+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23784+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23786+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23797+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23862+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23866+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23868+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23869+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.2387+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23872+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23874+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23875+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23877+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23878+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23879+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.2388+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23882+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23885+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23886+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23887+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23889+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.2389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23891+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23893+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23894+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23895+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23897+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23898+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23899+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23902+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23903+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23904+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23906+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.23907+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:30.23909+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:30.24033+08:00 INFO [359133,5c0117ead9a5c13a] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=5c0117ead9a5c13a, body=] 2023-04-29T13:19:30.24047+08:00 INFO [359133,bbf6e1a7ec53486b] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=bbf6e1a7ec53486b, body=] 2023-04-29T13:19:30.24122+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:19:30.24129+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:19:32.72578+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.396105ms 2023-04-29T13:19:32.72584+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:32.8244+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.128801ms 2023-04-29T13:19:32.82446+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:37.72686+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.878512ms 2023-04-29T13:19:37.72692+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:37.82548+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.573807ms 2023-04-29T13:19:37.82555+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:42.72683+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.421805ms 2023-04-29T13:19:42.7269+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:42.82527+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.937113ms 2023-04-29T13:19:42.82534+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:45.23651+08:00 INFO [359133,3e34a60a90b326e7] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=3e34a60a90b326e7, body=] 2023-04-29T13:19:45.23718+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:19:45.23723+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:19:45.24443+08:00 INFO [359133,3a822cbda4f0bdc1] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=3a822cbda4f0bdc1, body=] 2023-04-29T13:19:45.24474+08:00 INFO [359133,edd892e6322a6d00] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=edd892e6322a6d00, body=] 2023-04-29T13:19:45.24897+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.24901+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.24903+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.24904+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.24906+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.24907+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.24909+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.2491+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.24911+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.24913+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.24914+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.24915+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.24916+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.24918+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.24919+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.2492+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.24922+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.24923+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.24924+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.24926+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.24927+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.24928+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.24929+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.24931+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.24932+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.24933+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.24935+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.24936+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.24939+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.2494+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.24941+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.24943+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25008+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25011+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25013+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25014+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25015+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25017+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25018+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25019+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25021+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25022+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25023+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25025+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25026+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25029+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.2503+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25032+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25033+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25034+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25036+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25039+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.2504+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25042+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25043+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25044+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25046+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25047+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25048+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25049+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25051+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25052+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25053+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25055+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25057+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25058+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25059+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25061+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25062+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25063+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25064+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25066+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25067+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25068+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25069+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25071+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25072+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25073+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25074+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25076+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25082+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25083+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25086+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25087+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25089+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.2509+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25092+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25093+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25094+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25096+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25097+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25098+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.251+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25101+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25102+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25103+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25105+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25107+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25108+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25109+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25112+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25113+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25114+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25116+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25117+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25118+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25119+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25121+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25122+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25124+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25125+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25127+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25128+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25129+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25131+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25133+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25134+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25136+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25138+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.2514+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25141+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25142+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25144+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25145+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25146+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25148+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25149+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.2515+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25151+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25153+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25154+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25156+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:45.25157+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:19:45.25158+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:19:47.72688+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.843312ms 2023-04-29T13:19:47.72694+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:47.82567+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.989614ms 2023-04-29T13:19:47.82576+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:52.73512+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.638109ms 2023-04-29T13:19:52.73519+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:52.82487+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.681309ms 2023-04-29T13:19:52.82493+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:57.72641+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.823512ms 2023-04-29T13:19:57.72647+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:19:57.82542+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.512607ms 2023-04-29T13:19:57.82549+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:00.23698+08:00 INFO [359133,7d434cac51deedc1] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=7d434cac51deedc1, body=] 2023-04-29T13:20:00.23785+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23789+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.2379+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23793+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23812+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23813+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23816+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23821+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23822+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23825+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23826+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23834+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23838+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.2384+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23842+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23843+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23844+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23846+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23847+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23848+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.2385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23851+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23852+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23854+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23855+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23856+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23858+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23859+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.2386+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23861+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23863+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23864+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23865+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23866+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23868+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23869+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23872+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23873+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23875+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23876+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23878+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23879+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.2388+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23882+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23883+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23884+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23886+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23887+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23888+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.2389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23891+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23892+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23894+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23895+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23896+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23897+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23899+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23901+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23902+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23904+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23905+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23906+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23907+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23909+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.2391+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23911+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23912+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23914+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23915+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23916+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23918+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23919+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.2392+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23922+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23923+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23924+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23971+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23974+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23976+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23977+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23979+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.2398+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23981+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23984+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23985+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23986+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23988+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23989+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.2399+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23991+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23993+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23994+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23995+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23997+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.23998+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.23999+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.24001+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.24002+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.24003+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.24005+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.24006+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.24007+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.24008+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.2401+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.24011+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.24012+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.24014+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:00.24015+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:00.24122+08:00 INFO [359133,ed91ce177979f73d] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=ed91ce177979f73d, body=] 2023-04-29T13:20:00.24244+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:20:00.24253+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:20:00.24326+08:00 INFO [359133,e020a6d08e9b91cb] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=e020a6d08e9b91cb, body=] 2023-04-29T13:20:02.72725+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.874211ms 2023-04-29T13:20:02.72732+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:02.82698+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.241331ms 2023-04-29T13:20:02.82704+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:07.72643+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.0347ms 2023-04-29T13:20:07.72649+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:07.82456+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.478707ms 2023-04-29T13:20:07.82462+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:12.72686+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.71541ms 2023-04-29T13:20:12.72692+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:12.82467+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.272203ms 2023-04-29T13:20:12.82474+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:15.24112+08:00 INFO [359133,7206b14dd32f02a9] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=7206b14dd32f02a9, body=] 2023-04-29T13:20:15.24208+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24212+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24214+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24215+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24217+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24218+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.2422+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24221+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24222+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24224+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24225+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24226+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24228+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24229+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.2423+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.2424+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24242+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24243+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24245+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24246+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24247+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24248+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.2425+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24251+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24253+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24254+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24256+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24257+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24259+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.2426+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24262+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24263+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24264+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24265+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24267+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24268+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24269+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24271+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24272+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24273+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24274+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24276+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24277+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24278+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.2428+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24281+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24282+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24286+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24288+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24289+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24291+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24292+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24293+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24295+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24296+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24297+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24299+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.243+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24301+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24303+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24304+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24306+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24307+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24308+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.2431+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24311+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24312+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24313+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24315+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24316+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24317+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24319+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.2432+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24321+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24322+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24324+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24325+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24326+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24328+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24329+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24335+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24338+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24341+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24344+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24346+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24347+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24348+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.2435+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24351+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24352+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24353+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24355+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24356+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24357+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24359+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.2436+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24362+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24363+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24364+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24365+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24367+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24368+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24415+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24418+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24419+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24421+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24423+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24424+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24425+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24426+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24428+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24429+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24436+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24441+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24443+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24444+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24446+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24447+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24448+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.2445+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24451+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24452+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24454+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24455+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24457+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24458+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24459+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.2446+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24463+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24464+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24465+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24467+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24468+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:15.24469+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:15.24581+08:00 INFO [359133,238f3f853d5d1a07] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=238f3f853d5d1a07, body=] 2023-04-29T13:20:15.24591+08:00 INFO [359133,528233ce311bdc57] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=528233ce311bdc57, body=] 2023-04-29T13:20:15.24652+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:20:15.24655+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:20:17.72655+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.628908ms 2023-04-29T13:20:17.72662+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:17.82416+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.185802ms 2023-04-29T13:20:17.82422+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:22.72702+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.302318ms 2023-04-29T13:20:22.72709+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:22.82561+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.77321ms 2023-04-29T13:20:22.82567+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:27.7262+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.0667ms 2023-04-29T13:20:27.72628+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:27.82526+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.514807ms 2023-04-29T13:20:27.82533+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:30.23629+08:00 INFO [359133,1481daa10dfb7efe] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=1481daa10dfb7efe, body=] 2023-04-29T13:20:30.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23727+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23728+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23732+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23737+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.2376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23762+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23765+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23767+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23768+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23769+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23771+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23772+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23776+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23777+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23779+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.2378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23787+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23788+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23792+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23793+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23796+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23797+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23801+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23804+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23807+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23815+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23817+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23818+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23819+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23823+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23827+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23828+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.2383+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23831+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23835+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23838+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.2384+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23841+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23845+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23846+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23849+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.2385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23853+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.2386+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23862+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23863+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23908+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23911+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23913+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23915+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23917+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23918+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.2392+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23921+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23922+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23923+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23925+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23926+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23927+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23928+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.2393+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23931+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23932+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23934+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23935+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23936+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23939+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.2394+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23942+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23943+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23945+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23946+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23949+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23951+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23952+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23953+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.23954+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:30.23956+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:30.24054+08:00 INFO [359133,9018726aa1d14d6c] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=9018726aa1d14d6c, body=] 2023-04-29T13:20:30.24065+08:00 INFO [359133,65171d199a13402c] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=65171d199a13402c, body=] 2023-04-29T13:20:30.24153+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:20:30.24157+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:20:32.72682+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.603208ms 2023-04-29T13:20:32.72688+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:32.82409+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.908898ms 2023-04-29T13:20:32.82415+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:37.72812+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.822225ms 2023-04-29T13:20:37.72819+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:37.82574+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.036615ms 2023-04-29T13:20:37.8258+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:42.72931+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.362947ms 2023-04-29T13:20:42.7294+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:42.82799+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.111043ms 2023-04-29T13:20:42.82805+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:45.2361+08:00 INFO [359133,2600a66ceb467da4] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=2600a66ceb467da4, body=] 2023-04-29T13:20:45.23717+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23723+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23724+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23727+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23737+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23745+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23747+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23748+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23749+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23752+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23759+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.2376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23761+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23765+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23767+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23768+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23769+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23772+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23776+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23777+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23778+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.2378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23786+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23788+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23792+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23793+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23796+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23797+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23799+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.238+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23801+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23804+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23812+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23815+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23816+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23819+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.2382+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23821+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23823+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23824+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23825+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23826+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23828+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23829+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23834+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23837+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23839+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23841+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23845+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23846+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.2385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23857+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.2386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23906+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23914+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23915+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23917+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23918+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23919+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23921+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23922+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23923+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23924+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23926+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23927+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23928+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23929+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23934+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23936+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.2394+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23941+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23943+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23944+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23946+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23947+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23948+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23949+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23958+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.2396+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23961+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23963+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23964+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23965+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.23967+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:20:45.23968+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:20:45.24084+08:00 INFO [359133,a9ecd3cd6952a447] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=a9ecd3cd6952a447, body=] 2023-04-29T13:20:45.24097+08:00 INFO [359133,f0a518474fd030b0] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=f0a518474fd030b0, body=] 2023-04-29T13:20:45.24321+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:20:45.24327+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:20:47.72679+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.74701ms 2023-04-29T13:20:47.72686+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:47.82482+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.400205ms 2023-04-29T13:20:47.82488+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:52.73597+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.749224ms 2023-04-29T13:20:52.73603+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:52.81087+08:00 WARN [359133,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 384102 fields:, error="open /proc/384102/status: no such file or directory" 2023-04-29T13:20:52.81096+08:00 WARN [359133,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 384123 fields:, error="open /proc/384123/status: no such file or directory" 2023-04-29T13:20:52.82505+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.346604ms 2023-04-29T13:20:52.82512+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:57.73069+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.24336ms 2023-04-29T13:20:57.73076+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:20:57.82502+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.0545ms 2023-04-29T13:20:57.82508+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:00.23556+08:00 INFO [359133,d7d2e4d65fbd5b8f] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=d7d2e4d65fbd5b8f, body=] 2023-04-29T13:21:00.2365+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23655+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23657+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23658+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.2366+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23661+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23662+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23664+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23665+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23667+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23668+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23669+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23672+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23673+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23674+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23676+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23677+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.2368+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23682+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23683+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23684+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23685+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23687+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23688+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23689+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23691+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23692+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23693+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23695+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23696+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23697+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23698+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23701+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23707+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23711+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23715+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23718+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23727+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.2373+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23746+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.2375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23759+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.2376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23761+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23765+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23767+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23768+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.2377+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23771+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23772+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23774+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23775+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23776+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23778+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23779+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.2378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23782+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23783+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23787+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23788+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23791+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23792+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23793+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23795+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23796+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23797+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23857+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23864+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23866+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23867+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23868+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23871+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23872+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.2388+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23882+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23886+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23889+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.2389+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23891+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23893+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23894+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23896+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23897+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23898+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23901+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23902+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23904+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23905+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23906+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23907+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23909+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.2391+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.23911+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:00.23913+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:00.24026+08:00 INFO [359133,c857f606d4599ebd] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=c857f606d4599ebd, body=] 2023-04-29T13:21:00.24084+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:21:00.24088+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:21:00.2456+08:00 INFO [359133,90101dfab28ba943] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=90101dfab28ba943, body=] 2023-04-29T13:21:02.7267+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.905712ms 2023-04-29T13:21:02.72677+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:02.82524+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.562508ms 2023-04-29T13:21:02.82531+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:07.72917+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.55965ms 2023-04-29T13:21:07.72925+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:07.82611+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.770724ms 2023-04-29T13:21:07.82617+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:12.72611+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.480507ms 2023-04-29T13:21:12.72618+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:12.82475+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.0261ms 2023-04-29T13:21:12.82481+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:15.23558+08:00 INFO [359133,85026189284e5737] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=85026189284e5737, body=] 2023-04-29T13:21:15.23655+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.2366+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23661+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23663+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23664+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23665+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23667+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.2367+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23672+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23673+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23674+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23675+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23677+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23678+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23679+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23681+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23682+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23683+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23684+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23686+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23687+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23688+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.2369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23691+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23693+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23694+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23708+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23724+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23725+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23732+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23745+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23757+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23765+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23767+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23786+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23788+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23792+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23793+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23797+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23801+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23803+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23806+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23807+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.2381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23811+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.2382+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23823+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23839+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.2384+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23842+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23846+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23857+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23864+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23866+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23872+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23874+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23875+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23876+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23878+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23879+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.2388+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23881+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23883+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23884+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23956+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23962+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23966+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23967+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23969+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.2397+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23972+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23974+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23975+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23976+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23978+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23979+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.2398+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23982+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23983+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23984+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23986+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23987+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23989+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.2399+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23991+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23993+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23994+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23995+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23996+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.23998+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.23999+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.24001+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.24002+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.24003+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.24005+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:15.24007+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:15.24155+08:00 INFO [359133,3ef855dfc35aea08] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=3ef855dfc35aea08, body=] 2023-04-29T13:21:15.24167+08:00 INFO [359133,309ad7096bf61d44] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=309ad7096bf61d44, body=] 2023-04-29T13:21:15.24242+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:21:15.24246+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:21:17.72666+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.717309ms 2023-04-29T13:21:17.72674+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:17.82514+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.314404ms 2023-04-29T13:21:17.8252+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:22.72689+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.970513ms 2023-04-29T13:21:22.72696+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:22.82521+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.628408ms 2023-04-29T13:21:22.82528+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:27.72738+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.195116ms 2023-04-29T13:21:27.72745+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:27.82527+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.442906ms 2023-04-29T13:21:27.82534+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:30.23558+08:00 INFO [359133,068815047b48d013] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=068815047b48d013, body=] 2023-04-29T13:21:30.23653+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23657+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23659+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.2366+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23666+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23669+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.2367+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23672+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23673+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23675+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23676+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23677+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23678+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.2368+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23681+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23682+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23683+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23685+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23686+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23687+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23688+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.2369+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23691+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23692+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23694+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23695+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23696+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23698+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23699+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23702+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23707+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.2371+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23711+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23714+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23715+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23727+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23739+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23759+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23761+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23765+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23778+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23783+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23784+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23785+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23789+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.2379+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23793+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23794+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23795+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23798+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23799+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23845+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23849+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23851+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23852+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23853+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23855+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23856+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23857+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23859+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.2386+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23861+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23863+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23868+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23871+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23872+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23874+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23875+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23876+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23877+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23879+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.2388+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23881+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23882+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23884+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23885+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23886+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23888+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23889+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.2389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.23891+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:30.23893+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:30.24004+08:00 INFO [359133,6c8b9bf6cbfaad15] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=6c8b9bf6cbfaad15, body=] 2023-04-29T13:21:30.24016+08:00 INFO [359133,d3697684361a0baf] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=d3697684361a0baf, body=] 2023-04-29T13:21:30.24091+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:21:30.24094+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:21:32.72726+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.557221ms 2023-04-29T13:21:32.72732+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:32.82508+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.636409ms 2023-04-29T13:21:32.82514+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:37.72568+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.184102ms 2023-04-29T13:21:37.72579+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:37.82549+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.628709ms 2023-04-29T13:21:37.82555+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:42.73251+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.884669ms 2023-04-29T13:21:42.73258+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:42.82468+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.612308ms 2023-04-29T13:21:42.82474+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:45.23524+08:00 INFO [359133,cf90f536b47daf93] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=cf90f536b47daf93, body=] 2023-04-29T13:21:45.23688+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23697+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23699+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23702+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23705+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23706+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23708+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23709+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.2371+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23714+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.2372+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23725+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23737+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.2374+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23743+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23744+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23747+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23748+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23758+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23759+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23761+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23762+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23765+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23769+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.2377+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23773+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23774+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23775+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23777+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23778+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23785+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23793+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23801+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23804+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23806+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23807+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.2381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23812+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23813+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23816+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23819+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.2382+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23821+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23823+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23824+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23825+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23826+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23828+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23829+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23834+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23837+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.2384+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23841+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23843+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23844+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23845+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23847+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23848+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23849+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23851+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23852+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23853+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23855+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23909+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23912+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23914+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23915+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23917+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23919+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.2392+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23922+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23923+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23924+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23926+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23927+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23928+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.2393+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23931+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23933+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23934+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23936+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23938+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.2394+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23941+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23942+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23944+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23945+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23946+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23947+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23949+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.2395+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23951+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23952+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.23954+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:21:45.23956+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:21:45.2409+08:00 INFO [359133,e2abbe7956a1f32d] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=e2abbe7956a1f32d, body=] 2023-04-29T13:21:45.24105+08:00 INFO [359133,431d3613039a9649] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=431d3613039a9649, body=] 2023-04-29T13:21:45.24198+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:21:45.24202+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:21:47.72666+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.817612ms 2023-04-29T13:21:47.72672+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:47.8254+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.909112ms 2023-04-29T13:21:47.82546+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:52.76255+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.028527ms 2023-04-29T13:21:52.76261+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:52.82931+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.024171ms 2023-04-29T13:21:52.8295+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:57.72754+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.742224ms 2023-04-29T13:21:57.72763+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:21:57.82698+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.689737ms 2023-04-29T13:21:57.82705+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:00.23558+08:00 INFO [359133,9bc5a0367376bbed] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=9bc5a0367376bbed, body=] 2023-04-29T13:22:00.23664+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.2367+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23672+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23673+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23675+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23676+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23678+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23679+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.2368+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23682+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23686+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23688+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23691+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23693+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23698+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.237+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23715+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23718+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23725+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23739+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23741+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23745+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23746+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23752+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23761+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23768+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.2377+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23775+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23778+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.2378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23782+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23792+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23793+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23795+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23796+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23797+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.238+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23801+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23803+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23804+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23807+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23811+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23816+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23817+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.2384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23843+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23849+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23855+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.2386+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23865+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23948+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23952+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23954+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23955+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23957+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23958+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23959+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23961+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23963+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23967+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.2397+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23973+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23976+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23978+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.2398+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23981+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23984+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23985+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23988+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23989+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.2399+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23992+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23993+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23994+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23996+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.23997+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.23998+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.24001+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.24002+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.24003+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.24005+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:00.24006+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:00.24149+08:00 INFO [359133,9173622abeb5da9d] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=9173622abeb5da9d, body=] 2023-04-29T13:22:00.24164+08:00 INFO [359133,a476b8d7e54cf06b] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=a476b8d7e54cf06b, body=] 2023-04-29T13:22:00.24246+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:22:00.2425+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:22:02.72724+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.77781ms 2023-04-29T13:22:02.72739+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:02.83008+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.140272ms 2023-04-29T13:22:02.83015+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:07.73351+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.081114ms 2023-04-29T13:22:07.7336+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:07.82594+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.745424ms 2023-04-29T13:22:07.82604+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:12.72693+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.023814ms 2023-04-29T13:22:12.72701+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:12.82501+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.345004ms 2023-04-29T13:22:12.82508+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:15.23547+08:00 INFO [359133,c004f3252ecdccae] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=c004f3252ecdccae, body=] 2023-04-29T13:22:15.23833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23839+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23841+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23848+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.2385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23851+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23853+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23854+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23859+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23864+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23865+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23867+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23869+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23871+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23873+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23875+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23876+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23878+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23879+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23881+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23882+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.2389+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23894+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23896+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23898+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.239+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23902+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23913+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23915+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23917+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23919+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.2392+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23922+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23923+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23925+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23927+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23929+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.2393+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23932+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23933+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23935+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23936+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.2394+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23942+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23943+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23945+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23947+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.2395+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23953+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23955+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23957+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.2396+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23963+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23966+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23969+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23971+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.23988+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.23998+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24001+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24003+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24004+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24006+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24009+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.2401+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24012+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24015+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24018+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24022+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24024+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24025+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24028+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.2403+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24031+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24033+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24034+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24036+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.2404+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24042+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24044+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24045+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24046+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24048+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24049+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24051+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24059+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24061+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24062+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24064+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24066+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24068+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.2407+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24071+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24073+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24074+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24076+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24078+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24079+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24081+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24271+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24275+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24277+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24279+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.2428+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24282+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24292+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24298+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.243+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24301+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24303+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24304+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24306+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24309+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.2431+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24312+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24313+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24315+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24316+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24318+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.2432+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24322+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24323+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24325+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24327+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24328+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.2433+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24331+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24334+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.24335+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24336+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:15.2434+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:15.24566+08:00 INFO [359133,6799367a04874f83] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=6799367a04874f83, body=] 2023-04-29T13:22:15.24632+08:00 INFO [359133,06a09efcd0a388eb] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=06a09efcd0a388eb, body=] 2023-04-29T13:22:15.24712+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:22:15.24715+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:22:17.72646+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.393905ms 2023-04-29T13:22:17.72652+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:17.82476+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.76331ms 2023-04-29T13:22:17.82483+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:22.72747+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.094629ms 2023-04-29T13:22:22.72754+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:22.82481+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.793311ms 2023-04-29T13:22:22.82487+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:27.72728+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.45222ms 2023-04-29T13:22:27.72743+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:27.82533+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.137815ms 2023-04-29T13:22:27.82541+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:30.23745+08:00 INFO [359133,c4e4ec23026bb5f8] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=c4e4ec23026bb5f8, body=] 2023-04-29T13:22:30.23838+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23846+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23849+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.2385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23853+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23857+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23861+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23862+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23865+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.2387+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23872+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23873+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.2388+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23881+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23883+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23884+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23885+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23887+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23888+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23889+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.2389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23892+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23893+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23894+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23896+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23897+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23898+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.239+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23901+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23902+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23904+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23905+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23906+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23908+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23909+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.2391+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23912+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23913+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23914+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23916+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23917+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23918+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23919+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23921+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23922+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23924+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23925+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23926+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23928+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23929+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.2393+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23932+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23933+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23934+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23935+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23937+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.2394+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23941+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23942+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23944+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23945+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23947+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23948+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23949+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23951+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23952+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23953+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23955+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23956+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23957+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23958+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.2396+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23961+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23962+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23964+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23965+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23971+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23972+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23973+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23975+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23976+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23978+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23979+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23981+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23982+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23983+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23984+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23986+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23987+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23989+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.2399+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.23992+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.23994+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.24046+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.24049+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.24051+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.24052+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.24054+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.24055+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.24056+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.24058+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.24059+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.2406+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.24062+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.24063+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.24065+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.2407+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.24072+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.24073+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.24074+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.24076+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.24077+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.24079+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.2408+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.24082+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.24083+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.24084+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.24086+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.24087+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.24088+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.24089+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.24091+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.24092+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.24093+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:30.24095+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:30.24209+08:00 INFO [359133,ba567a7db6507a81] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=ba567a7db6507a81, body=] 2023-04-29T13:22:30.24263+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:22:30.2427+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:22:30.24709+08:00 INFO [359133,7399ce308db1e595] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=7399ce308db1e595, body=] 2023-04-29T13:22:32.72647+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.408606ms 2023-04-29T13:22:32.72653+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:32.82564+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.423819ms 2023-04-29T13:22:32.82571+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:37.72969+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.664451ms 2023-04-29T13:22:37.72979+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:37.82458+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.592608ms 2023-04-29T13:22:37.82465+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:42.72672+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.685009ms 2023-04-29T13:22:42.7268+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:42.82487+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.344804ms 2023-04-29T13:22:42.82493+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:45.23553+08:00 INFO [359133,80570a8c70672737] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=80570a8c70672737, body=] 2023-04-29T13:22:45.2364+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23647+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.2365+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23651+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23653+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23654+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23655+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23657+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23658+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.2366+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23661+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23662+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23664+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23665+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23666+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.2367+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23671+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23673+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23674+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23675+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23677+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23678+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23679+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23681+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23682+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23683+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23685+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23686+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23687+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23689+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.2369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23691+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23693+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23694+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23697+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23698+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23701+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23711+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23721+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23727+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.2373+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23734+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23736+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23739+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.2374+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23743+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23744+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23747+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23748+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23752+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23761+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23762+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23765+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23768+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23769+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23772+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23775+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23776+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23777+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23779+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.2378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23783+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23787+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23788+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23846+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23849+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.2385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23852+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23853+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23856+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23857+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.2386+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23861+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23862+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23864+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23865+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23867+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23868+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23869+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23872+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23873+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23874+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23876+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23877+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23878+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.2388+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23881+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23883+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23886+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.23887+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:22:45.23888+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:22:45.24001+08:00 INFO [359133,7821ee1f242ef2c5] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=7821ee1f242ef2c5, body=] 2023-04-29T13:22:45.24016+08:00 INFO [359133,4b2a5f771e05d5f5] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=4b2a5f771e05d5f5, body=] 2023-04-29T13:22:45.24094+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:22:45.24098+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:22:47.72687+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.524107ms 2023-04-29T13:22:47.72694+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:47.8255+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.010014ms 2023-04-29T13:22:47.82556+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:52.7736+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.241431ms 2023-04-29T13:22:52.77367+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:52.82514+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.873912ms 2023-04-29T13:22:52.82521+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:57.72729+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.200817ms 2023-04-29T13:22:57.72736+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:22:57.82551+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.542607ms 2023-04-29T13:22:57.82557+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:00.23815+08:00 INFO [359133,33ffa9fbb9c464ca] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=33ffa9fbb9c464ca, body=] 2023-04-29T13:23:00.23918+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23922+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23924+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23925+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23927+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23928+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23929+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23931+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23932+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23933+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23935+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23936+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.2394+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23941+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23943+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23944+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23945+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23947+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23948+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.2395+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23951+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23952+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23954+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23955+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23956+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23957+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23959+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.2396+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23961+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23962+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23964+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23965+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23966+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23967+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23969+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.2397+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23971+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23972+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23974+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23975+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23976+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23977+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23979+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.2398+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23984+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23986+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23987+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23989+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.2399+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23991+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23993+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23994+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23995+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23996+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.23998+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.23999+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24001+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24003+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24004+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24009+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24011+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24012+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24013+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24015+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24016+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24017+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24018+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.2402+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24021+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24022+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24024+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24025+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24026+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24027+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24029+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.2403+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24032+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24033+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24034+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24036+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24039+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.2404+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24041+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24043+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24044+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24045+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24047+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24048+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24049+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24051+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24052+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24053+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24054+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24056+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24057+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24058+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24059+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24061+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24062+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24064+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24065+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24114+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24117+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24119+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.2412+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24121+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24123+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24124+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24125+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24126+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24128+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24129+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24131+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24132+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24133+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24135+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24136+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24139+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.2414+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24142+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24143+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24144+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24146+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24147+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24149+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.2415+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24151+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24152+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24154+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24155+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24156+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24158+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:00.24159+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:00.24266+08:00 INFO [359133,45658dd27a36b586] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=45658dd27a36b586, body=] 2023-04-29T13:23:00.24278+08:00 INFO [359133,caab88756753840d] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=caab88756753840d, body=] 2023-04-29T13:23:00.24353+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:23:00.24361+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:23:02.72658+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.985614ms 2023-04-29T13:23:02.7267+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:02.82522+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.917013ms 2023-04-29T13:23:02.82529+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:07.72815+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.721724ms 2023-04-29T13:23:07.72822+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:07.82546+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.845711ms 2023-04-29T13:23:07.82553+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:12.72727+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.874212ms 2023-04-29T13:23:12.72733+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:12.82591+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.057314ms 2023-04-29T13:23:12.82599+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:15.23601+08:00 INFO [359133,f5ba8fa23cf4b810] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=f5ba8fa23cf4b810, body=] 2023-04-29T13:23:15.23694+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23699+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23702+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23706+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23707+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23709+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23711+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23712+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23718+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23727+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23737+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23739+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23743+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23744+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23747+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23748+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.2376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23762+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23766+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23767+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23768+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23769+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23771+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23772+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23775+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23776+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23777+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23779+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.2378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23783+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23786+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23788+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23792+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23794+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23795+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23796+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23798+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23799+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.238+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23802+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23803+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23804+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23806+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23807+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23811+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23816+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23817+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23818+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23829+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.2383+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23831+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23833+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23882+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23885+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23887+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23888+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23889+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23891+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23892+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23894+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23896+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23897+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23898+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23899+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23901+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23902+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23903+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23905+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23906+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23907+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23908+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.2391+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23911+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23912+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23914+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23915+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23916+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23918+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23919+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.2392+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23921+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23923+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.23924+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:15.23925+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:15.24035+08:00 INFO [359133,2e60692a9e916f81] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=2e60692a9e916f81, body=] 2023-04-29T13:23:15.2405+08:00 INFO [359133,bbb219f1e45e6b2a] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=bbb219f1e45e6b2a, body=] 2023-04-29T13:23:15.2412+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:23:15.24124+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:23:17.7267+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.105415ms 2023-04-29T13:23:17.72677+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:17.82525+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.550708ms 2023-04-29T13:23:17.82531+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:22.72693+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.598708ms 2023-04-29T13:23:22.72701+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:22.82556+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.607808ms 2023-04-29T13:23:22.82562+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:27.72704+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.980713ms 2023-04-29T13:23:27.7271+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:27.82695+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.859826ms 2023-04-29T13:23:27.82703+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:30.23643+08:00 INFO [359133,26eab1b6f9dd7ffb] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=26eab1b6f9dd7ffb, body=] 2023-04-29T13:23:30.23661+08:00 INFO [359133,2a08cbf3e2a05517] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=2a08cbf3e2a05517, body=] 2023-04-29T13:23:30.23719+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:23:30.23723+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:23:30.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23852+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23856+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23861+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23863+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23866+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23867+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23868+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23871+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23872+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23874+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23875+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23876+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23878+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23879+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.2388+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23882+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23883+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23884+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23886+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23887+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23888+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23889+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23895+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23898+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23902+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23904+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23906+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23907+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23909+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23911+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23913+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23914+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23916+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23917+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23918+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.2392+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23921+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23922+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23924+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23925+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23927+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23929+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23931+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23932+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23934+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23936+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23939+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23941+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23942+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23943+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.2395+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23951+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23953+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23954+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23955+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23957+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23958+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23959+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23961+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23962+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23963+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23965+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23966+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23968+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23969+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.2397+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23972+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23973+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23975+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23976+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23977+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23979+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.2398+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23981+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23983+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23984+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23985+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23986+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23988+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23989+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.2399+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23992+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23993+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23994+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23996+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.23997+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.23999+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.24+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.24004+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.24006+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.24007+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.24009+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.2401+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.24011+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.24013+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.24014+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.24016+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.24017+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.24076+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.2408+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.24082+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.24083+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.24084+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.24086+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.24087+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.24089+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.2409+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.24091+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.24093+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.24094+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.24095+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.24096+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.24098+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.24099+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.241+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.24101+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.24103+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.24104+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.24105+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.24107+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.24108+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.2411+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.24112+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.24113+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.24115+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.24116+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.24117+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.24119+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.2412+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:30.24121+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:30.24709+08:00 INFO [359133,f05b4b376790cd0d] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=f05b4b376790cd0d, body=] 2023-04-29T13:23:32.7277+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.315618ms 2023-04-29T13:23:32.72778+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:32.82651+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.114329ms 2023-04-29T13:23:32.82657+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:37.72682+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.694409ms 2023-04-29T13:23:37.72688+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:37.82607+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.41112ms 2023-04-29T13:23:37.82614+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:42.72616+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.75101ms 2023-04-29T13:23:42.72622+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:42.82523+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.568008ms 2023-04-29T13:23:42.82529+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:45.23577+08:00 INFO [359133,1f87e7b4f2f4abfd] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=1f87e7b4f2f4abfd, body=] 2023-04-29T13:23:45.23667+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23671+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23673+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23674+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23676+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23677+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23679+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.2368+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23681+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23683+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23684+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23685+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23687+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23688+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23689+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.2369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23692+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23693+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23694+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23696+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23697+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23698+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23701+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23711+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23715+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23727+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.2373+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23734+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23739+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23741+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23745+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23746+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23749+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.2375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23754+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23758+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23759+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.2376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23762+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23766+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23767+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23768+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.2377+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23778+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.2378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23783+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23786+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23793+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23796+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23797+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.238+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23801+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23804+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23811+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23816+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23886+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.2389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23891+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23893+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23894+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23896+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23901+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23902+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23904+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23907+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23908+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23909+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23911+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23912+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23913+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23915+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23916+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23917+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23919+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.2392+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23925+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23927+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23928+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23929+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23931+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23932+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23933+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23935+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23936+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23939+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.23941+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:23:45.23942+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:23:45.24054+08:00 INFO [359133,1d745dd4fb6bf9fa] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=1d745dd4fb6bf9fa, body=] 2023-04-29T13:23:45.24109+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:23:45.24112+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:23:45.24553+08:00 INFO [359133,e380381ab9a1dfd1] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=e380381ab9a1dfd1, body=] 2023-04-29T13:23:47.72667+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.467006ms 2023-04-29T13:23:47.72674+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:47.8263+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.114229ms 2023-04-29T13:23:47.82639+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:52.75547+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.176716ms 2023-04-29T13:23:52.75554+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:52.82561+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.191016ms 2023-04-29T13:23:52.82568+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:57.72644+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.520006ms 2023-04-29T13:23:57.72656+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:23:57.82543+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.423505ms 2023-04-29T13:23:57.8255+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:00.23604+08:00 INFO [359133,4f9430c5fc639283] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=4f9430c5fc639283, body=] 2023-04-29T13:24:00.23626+08:00 INFO [359133,da19eadd7752db00] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=da19eadd7752db00, body=] 2023-04-29T13:24:00.23781+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:24:00.23788+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:24:00.23979+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.23983+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.23985+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.23986+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.23988+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.23989+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.2399+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.23991+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.23993+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.23994+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.23995+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.23997+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.23998+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.23999+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24002+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24004+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24005+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24006+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24007+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24009+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.2401+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24011+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24013+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24015+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24016+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24018+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24026+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24028+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24029+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24031+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24032+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24033+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24035+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24036+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24039+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.2404+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24042+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24043+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24045+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24046+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24047+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24049+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.2405+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24051+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24052+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24054+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24055+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24056+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24057+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24059+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.2406+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24061+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24063+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24064+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24068+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.2407+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24072+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24073+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24076+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24077+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.2408+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24082+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24083+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24085+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24086+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24087+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24089+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.2409+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24091+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24092+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24094+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24095+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24096+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24098+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24099+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.241+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24102+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24103+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24104+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24108+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24109+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24111+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24114+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24115+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24116+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24118+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24119+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.2412+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24125+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24127+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24128+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.2413+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24132+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24133+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24134+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24135+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24137+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24142+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24144+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24145+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24146+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24213+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24216+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24218+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24219+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24225+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24227+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24229+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.2423+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24231+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24234+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24236+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.2424+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24242+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24243+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24244+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24246+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24248+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.2425+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24251+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24253+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24254+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24256+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24258+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24259+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24261+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24262+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24263+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24265+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24266+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24267+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:00.24269+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:00.24973+08:00 INFO [359133,dc15b5d7501bf025] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=dc15b5d7501bf025, body=] 2023-04-29T13:24:02.72652+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.388205ms 2023-04-29T13:24:02.72658+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:02.82641+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.575422ms 2023-04-29T13:24:02.82647+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:07.72617+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.537707ms 2023-04-29T13:24:07.72623+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:07.82534+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.442506ms 2023-04-29T13:24:07.82541+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:12.72663+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.683809ms 2023-04-29T13:24:12.7267+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:12.82542+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.291318ms 2023-04-29T13:24:12.82553+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:15.2355+08:00 INFO [359133,e46a0040d3c10541] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=e46a0040d3c10541, body=] 2023-04-29T13:24:15.23634+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.2364+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23642+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23643+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23644+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23646+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23647+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23649+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.2365+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23652+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23653+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23654+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23656+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23657+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23658+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.2366+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23661+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23662+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23664+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23666+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23668+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23669+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.2367+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23671+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23673+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23675+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23676+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23678+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23679+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.2368+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23682+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23683+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23685+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23686+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23687+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23689+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.2369+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23691+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23692+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23694+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23695+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23696+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23697+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23699+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23701+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23707+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23721+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23727+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23738+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23743+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23747+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.2376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23762+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23765+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23822+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23828+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23829+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23831+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23834+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23835+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23839+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23841+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23842+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23843+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23846+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23847+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.2385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23851+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23853+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23854+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23855+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23856+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23858+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.2386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23862+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23864+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23865+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23866+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23867+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:15.23869+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:15.23998+08:00 INFO [359133,64e9e47546c3e879] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=64e9e47546c3e879, body=] 2023-04-29T13:24:15.24065+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:24:15.24069+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:24:15.24572+08:00 INFO [359133,8d8afafba5f334f9] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=8d8afafba5f334f9, body=] 2023-04-29T13:24:17.72699+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.786311ms 2023-04-29T13:24:17.72709+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:17.82648+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.036929ms 2023-04-29T13:24:17.82655+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:22.72647+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.267003ms 2023-04-29T13:24:22.72655+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:22.82547+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.637908ms 2023-04-29T13:24:22.82554+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:27.72674+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.770611ms 2023-04-29T13:24:27.7268+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:27.82483+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.617908ms 2023-04-29T13:24:27.82489+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:30.23542+08:00 INFO [359133,389f1e1655c90818] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=389f1e1655c90818, body=] 2023-04-29T13:24:30.23631+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23635+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23638+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.2364+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23641+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23643+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23644+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23646+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23647+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23648+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.2365+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23651+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23652+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23654+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23655+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23656+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23658+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23659+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.2366+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23662+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23663+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23665+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23667+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23669+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23671+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23672+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23673+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23675+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23681+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23682+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23684+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23685+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23686+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23687+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23689+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.2369+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23691+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23693+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23694+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23696+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23697+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23698+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23699+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23701+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23702+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23705+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23706+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23707+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23709+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.2371+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23711+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23713+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23715+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23716+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23717+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23719+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.2372+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23723+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23724+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23725+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23727+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23728+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23729+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23732+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23733+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23736+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23757+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23758+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.2376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23761+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23762+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23765+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23769+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23773+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23783+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23839+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23842+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.2385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.2386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23862+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23865+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23866+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23868+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23869+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23872+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23873+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23874+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.2388+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23881+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23883+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23884+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23885+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.23887+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:30.23892+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:30.24061+08:00 INFO [359133,1592faf5d259b2cd] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=1592faf5d259b2cd, body=] 2023-04-29T13:24:30.24073+08:00 INFO [359133,b3707e8671e3d529] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=b3707e8671e3d529, body=] 2023-04-29T13:24:30.24152+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:24:30.24155+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:24:32.72819+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.257331ms 2023-04-29T13:24:32.72825+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:32.82558+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.904513ms 2023-04-29T13:24:32.82565+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:37.72809+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.020728ms 2023-04-29T13:24:37.72817+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:37.82541+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.198316ms 2023-04-29T13:24:37.82548+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:42.72694+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.519807ms 2023-04-29T13:24:42.72703+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:42.82523+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.788611ms 2023-04-29T13:24:42.82531+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:45.23638+08:00 INFO [359133,41d3ddc30beb0dfe] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=41d3ddc30beb0dfe, body=] 2023-04-29T13:24:45.24166+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24173+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24175+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24177+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24179+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24182+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24183+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24185+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24187+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24188+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.2419+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24191+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24193+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24195+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24196+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24198+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24199+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24201+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24203+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24205+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24206+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24208+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.2422+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24221+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24223+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24225+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24226+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24249+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24257+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24259+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24261+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24262+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24264+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24266+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24268+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24269+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24271+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24273+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24275+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24278+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.2428+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24281+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24283+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24284+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24286+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24287+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.2429+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24291+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24293+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24294+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24296+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24299+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24301+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24303+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24304+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24306+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24307+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24309+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.2431+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24312+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24323+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24325+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24327+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24329+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.2433+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24332+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24333+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24335+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24336+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24344+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24346+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24347+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24349+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24351+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24352+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24354+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24355+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24357+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24363+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24365+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24366+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24367+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24369+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24371+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24373+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24377+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24379+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24388+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24389+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24391+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24393+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24394+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24396+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24398+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24399+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.244+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24604+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24609+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24611+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24617+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.2462+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24621+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24623+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24625+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24632+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24633+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24635+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24636+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24649+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24653+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24654+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24656+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24658+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24664+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24666+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24669+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24671+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24673+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24674+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24676+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24682+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24684+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24685+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24687+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24688+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.2469+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.24691+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:24:45.24693+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:24:45.25006+08:00 INFO [359133,83eb520726d02625] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=83eb520726d02625, body=] 2023-04-29T13:24:45.25088+08:00 INFO [359133,81ee7130514c3228] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=81ee7130514c3228, body=] 2023-04-29T13:24:45.25184+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:24:45.25188+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:24:47.7284+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.554636ms 2023-04-29T13:24:47.72854+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:47.83233+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=14.343004ms 2023-04-29T13:24:47.83241+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:52.74213+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.316047ms 2023-04-29T13:24:52.74221+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:52.82925+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.01157ms 2023-04-29T13:24:52.82932+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:57.72722+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.318018ms 2023-04-29T13:24:57.7273+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:24:57.82526+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.531107ms 2023-04-29T13:24:57.82532+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:00.23588+08:00 INFO [359133,9167d8eb1a843f75] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=9167d8eb1a843f75, body=] 2023-04-29T13:25:00.2361+08:00 INFO [359133,220c24a1434b32a5] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=220c24a1434b32a5, body=] 2023-04-29T13:25:00.23674+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:25:00.23678+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:25:00.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23777+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23779+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23781+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23782+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23784+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23785+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23786+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23791+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23793+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23794+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23802+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23806+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23816+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23817+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23818+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23827+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23829+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.2383+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23831+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23834+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23835+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23839+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23841+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23845+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23846+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.2385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23853+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23857+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23858+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.2386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23862+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23863+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23865+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23866+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23867+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23869+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23871+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23873+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23874+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23875+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23877+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23878+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23879+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23881+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23882+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23883+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23885+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23887+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23888+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23889+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23901+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23902+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23903+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23904+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23906+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23907+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23908+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.2391+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23915+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23916+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23918+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23919+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.2392+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23921+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23923+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23924+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23925+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23926+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23928+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23929+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23931+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23932+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23933+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23935+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23989+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23992+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23994+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23996+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.23997+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.23998+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.24+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.24001+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.24003+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.24004+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.24005+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.24006+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.24008+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.24009+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.2401+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.24016+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.24017+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.24018+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.2402+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.24021+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.24022+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.24024+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.24025+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.24026+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.24028+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.24029+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.2403+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.24032+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.24033+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.24034+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.24035+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:00.24037+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:00.24962+08:00 INFO [359133,7079e61b2602f2a6] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=7079e61b2602f2a6, body=] 2023-04-29T13:25:02.72956+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.403448ms 2023-04-29T13:25:02.72963+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:02.82546+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.356019ms 2023-04-29T13:25:02.82553+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:07.7275+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.425906ms 2023-04-29T13:25:07.72758+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:07.82519+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.197916ms 2023-04-29T13:25:07.82525+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:12.72947+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.301047ms 2023-04-29T13:25:12.72954+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:12.82463+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.252603ms 2023-04-29T13:25:12.8247+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:15.23537+08:00 INFO [359133,d0cedcfb8a78c7e2] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=d0cedcfb8a78c7e2, body=] 2023-04-29T13:25:15.23643+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23654+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23656+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23659+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23662+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23664+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23666+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23667+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.2367+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23671+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23672+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23674+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23675+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23677+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23678+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.2368+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23681+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23682+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23685+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23687+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23688+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23689+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.2369+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23692+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23693+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23694+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23695+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23697+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23698+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23699+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23701+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23702+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23704+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23705+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23706+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23707+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23709+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.2371+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23711+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23714+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23715+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23717+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23718+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23725+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23727+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.2373+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23738+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23744+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23762+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23765+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23769+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23777+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23778+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23783+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23784+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23785+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23789+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.2379+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23793+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23794+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23798+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23799+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23802+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23803+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23859+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23863+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23865+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23866+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23867+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23869+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.2387+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23872+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23873+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23875+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23876+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23877+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23879+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.2388+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23881+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23882+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23884+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23885+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23886+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23887+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23889+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.2389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23891+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23893+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23894+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23895+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23897+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23898+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23899+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.23902+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:15.23903+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:15.24033+08:00 INFO [359133,23bb86af35137494] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=23bb86af35137494, body=] 2023-04-29T13:25:15.24095+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:25:15.241+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:25:15.24516+08:00 INFO [359133,59526c8b69a5518a] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=59526c8b69a5518a, body=] 2023-04-29T13:25:17.72827+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.18973ms 2023-04-29T13:25:17.72834+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:17.8273+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.455734ms 2023-04-29T13:25:17.82737+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:22.7269+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.173716ms 2023-04-29T13:25:22.72698+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:22.82515+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.247102ms 2023-04-29T13:25:22.82523+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:27.72694+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.248317ms 2023-04-29T13:25:27.727+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:27.8251+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.673509ms 2023-04-29T13:25:27.82516+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:30.2353+08:00 INFO [359133,aa28f965964201cf] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=aa28f965964201cf, body=] 2023-04-29T13:25:30.23624+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23629+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23631+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23634+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23636+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23639+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23641+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23642+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23644+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23645+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23646+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23647+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23649+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.2365+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23651+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23653+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23654+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23655+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23656+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23658+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23659+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23661+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23662+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23663+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23664+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23666+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23667+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.2367+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23671+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23672+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23674+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23675+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23676+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23677+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23679+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.2368+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23681+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23683+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23684+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23686+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23687+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23688+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.2369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23691+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23696+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23698+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23699+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23701+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23702+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23711+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23715+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23719+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23727+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23738+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23743+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23747+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23761+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23762+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23773+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23777+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23778+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23833+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23837+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.2384+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23841+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23844+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23845+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23846+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23848+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23849+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.2385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23853+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.2386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23864+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23865+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23866+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23868+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23869+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.2387+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23872+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.23873+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:30.23875+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:30.2399+08:00 INFO [359133,c6e5f3d09c4e792d] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=c6e5f3d09c4e792d, body=] 2023-04-29T13:25:30.24006+08:00 INFO [359133,d90ec07558e54f98] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=d90ec07558e54f98, body=] 2023-04-29T13:25:30.24074+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:25:30.24078+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:25:32.728+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.954427ms 2023-04-29T13:25:32.72807+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:32.82596+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.504321ms 2023-04-29T13:25:32.82609+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:37.7269+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.899712ms 2023-04-29T13:25:37.72696+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:37.82525+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.525706ms 2023-04-29T13:25:37.82532+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:42.72782+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.657623ms 2023-04-29T13:25:42.7279+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:42.82675+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.620537ms 2023-04-29T13:25:42.82681+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:45.23615+08:00 INFO [359133,0a70b53c8dbfed93] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=0a70b53c8dbfed93, body=] 2023-04-29T13:25:45.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23713+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23714+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23716+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23717+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23718+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.2372+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23724+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23725+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23728+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23738+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.2376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23761+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23765+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23769+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.2377+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23776+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23777+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23778+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.2378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23786+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23788+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23792+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23793+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23797+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23801+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23816+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23817+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23818+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23832+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23834+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23839+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.2384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23843+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23846+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23848+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23849+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23851+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23852+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23853+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.2386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23862+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23864+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23866+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23867+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23869+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23922+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23925+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23926+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23928+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23929+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23931+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23932+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23933+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23935+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23936+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23939+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.2394+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23942+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23943+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23945+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23946+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23947+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23949+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.2395+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23951+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23953+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23954+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23955+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.2396+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23962+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23963+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23965+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23966+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.23967+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23968+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.2397+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:25:45.23971+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:25:45.24083+08:00 INFO [359133,629ff1dd677f6932] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=629ff1dd677f6932, body=] 2023-04-29T13:25:45.24096+08:00 INFO [359133,acc432af67dcc342] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=acc432af67dcc342, body=] 2023-04-29T13:25:45.24178+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:25:45.24182+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:25:47.7276+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.558021ms 2023-04-29T13:25:47.72767+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:47.82765+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.660151ms 2023-04-29T13:25:47.82772+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:52.77414+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=29.049813ms 2023-04-29T13:25:52.77421+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:52.8259+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.815525ms 2023-04-29T13:25:52.82597+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:57.73336+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.007099ms 2023-04-29T13:25:57.73345+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:25:57.82805+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.362648ms 2023-04-29T13:25:57.82812+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:00.23528+08:00 INFO [359133,a9a4346f91d4e45f] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=a9a4346f91d4e45f, body=] 2023-04-29T13:26:00.23627+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23632+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23634+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23635+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23637+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23639+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23641+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23642+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23644+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23645+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23647+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23649+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.2365+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23652+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23653+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23654+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23656+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23657+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23659+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.2366+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23661+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23662+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23664+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23665+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23666+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23667+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23669+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.2367+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23671+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23673+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23675+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23676+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23677+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23678+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.2368+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23681+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23682+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23683+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23685+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23686+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23688+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23689+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.2369+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23692+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23693+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23694+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23695+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23697+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23698+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23699+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23702+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23706+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23707+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23711+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23738+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.2376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23762+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23769+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23829+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23831+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23834+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23835+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.2384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23841+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23842+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23846+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.2385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23853+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23854+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23857+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23858+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.2386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23862+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23864+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23865+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23866+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23868+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23869+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23871+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:00.23872+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:00.23986+08:00 INFO [359133,4ec62ba7b5a89cca] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=4ec62ba7b5a89cca, body=] 2023-04-29T13:26:00.23999+08:00 INFO [359133,ef56348cd15348d0] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=ef56348cd15348d0, body=] 2023-04-29T13:26:00.24073+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:26:00.24076+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:26:02.72652+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.931112ms 2023-04-29T13:26:02.72659+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:02.82482+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.869212ms 2023-04-29T13:26:02.82489+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:07.7268+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.841911ms 2023-04-29T13:26:07.72687+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:07.82492+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.648409ms 2023-04-29T13:26:07.82499+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:12.73593+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.797239ms 2023-04-29T13:26:12.73601+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:12.82649+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.12623ms 2023-04-29T13:26:12.82656+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:15.23553+08:00 INFO [359133,1bbadf02eb5d554f] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=1bbadf02eb5d554f, body=] 2023-04-29T13:26:15.23688+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23694+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23696+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23697+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23699+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.237+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23703+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23721+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23727+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23733+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23734+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23737+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.2374+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23741+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23744+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23754+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23759+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.2376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23761+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23765+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23767+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23768+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23769+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23771+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23772+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23774+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23778+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23786+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23787+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23789+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.2379+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23793+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23794+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.2381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23811+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23816+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23829+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.2383+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23832+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23833+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23838+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23842+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23854+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23855+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23857+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23858+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.2386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.2394+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23948+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.2395+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23955+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23956+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23958+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23959+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.2396+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23962+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23963+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23964+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23966+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23967+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23969+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.2397+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23972+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23973+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23974+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23976+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23977+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23978+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23982+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23983+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.23984+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.23987+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.24004+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.24007+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.24008+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.2401+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.24011+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.24013+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:15.24014+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:15.24129+08:00 INFO [359133,56d540ffe81b4bfa] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=56d540ffe81b4bfa, body=] 2023-04-29T13:26:15.24146+08:00 INFO [359133,6f045b02d9696d9b] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=6f045b02d9696d9b, body=] 2023-04-29T13:26:15.24216+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:26:15.24219+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:26:17.72849+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.593936ms 2023-04-29T13:26:17.72856+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:17.82651+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.50232ms 2023-04-29T13:26:17.82666+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:22.72758+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.579722ms 2023-04-29T13:26:22.72765+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:22.82518+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.74781ms 2023-04-29T13:26:22.82524+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:27.73015+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.740152ms 2023-04-29T13:26:27.73022+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:27.8263+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.619722ms 2023-04-29T13:26:27.8264+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:30.23581+08:00 INFO [359133,dc2503d70168f029] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=dc2503d70168f029, body=] 2023-04-29T13:26:30.23679+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23684+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23685+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23687+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23688+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23689+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23691+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23692+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23693+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23696+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23698+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23699+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.237+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23703+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23707+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23708+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23715+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23721+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23722+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23739+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23741+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23743+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23744+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23745+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23747+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23748+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23749+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23752+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23753+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23756+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23757+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23758+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.2376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23761+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23765+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23773+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23777+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23781+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23783+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23784+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23785+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23789+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23795+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23796+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23798+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23799+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.238+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23802+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23803+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23804+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23806+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23807+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.2381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23811+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23816+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23817+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23884+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23888+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.2389+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23891+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23893+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23894+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23897+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23898+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.239+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23901+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23902+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23904+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23905+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23906+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23908+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23909+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.2391+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23912+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23913+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23915+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23916+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23918+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23919+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.2392+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23921+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23923+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23924+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23925+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23927+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23929+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.23931+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:30.23932+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:30.24043+08:00 INFO [359133,eed93f262821f107] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=eed93f262821f107, body=] 2023-04-29T13:26:30.24056+08:00 INFO [359133,961416374bb09398] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=961416374bb09398, body=] 2023-04-29T13:26:30.24122+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:26:30.24125+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:26:32.72751+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.839426ms 2023-04-29T13:26:32.72759+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:32.82472+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.489107ms 2023-04-29T13:26:32.82479+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:37.72593+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.371005ms 2023-04-29T13:26:37.72611+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:37.82536+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.917312ms 2023-04-29T13:26:37.82544+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:42.7268+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.644508ms 2023-04-29T13:26:42.72694+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:42.82461+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.251103ms 2023-04-29T13:26:42.82468+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:45.23571+08:00 INFO [359133,3f9ee82587d1674e] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=3f9ee82587d1674e, body=] 2023-04-29T13:26:45.2367+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23674+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23676+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23677+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23678+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.2368+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23681+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23682+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23684+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23685+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23686+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23688+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23689+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.2369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23691+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23693+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23694+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23696+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23698+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23699+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23701+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23707+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23711+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23715+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23718+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23721+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23722+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23727+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23737+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23748+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.2376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23762+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23767+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23768+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23769+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23771+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23772+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23778+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23781+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23783+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23784+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23785+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23789+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.2381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23812+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23813+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23872+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23876+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23877+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23878+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.2388+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23881+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23883+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23884+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23885+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23886+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23888+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23889+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.2389+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23892+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23893+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23895+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23896+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23897+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23899+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23901+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23903+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23904+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23905+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23906+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23908+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23909+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.2391+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23911+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23913+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.23914+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:26:45.23915+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:26:45.24034+08:00 INFO [359133,07a5f2f90ff7164e] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=07a5f2f90ff7164e, body=] 2023-04-29T13:26:45.24052+08:00 INFO [359133,4e77f22255023a29] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=4e77f22255023a29, body=] 2023-04-29T13:26:45.24119+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:26:45.24123+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:26:47.72659+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.063314ms 2023-04-29T13:26:47.72667+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:47.82461+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.292804ms 2023-04-29T13:26:47.82468+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:52.77274+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=42.673406ms 2023-04-29T13:26:52.77281+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:52.82472+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.526807ms 2023-04-29T13:26:52.82482+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:57.72717+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.75271ms 2023-04-29T13:26:57.72724+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:26:57.82493+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.76741ms 2023-04-29T13:26:57.82499+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:00.23546+08:00 INFO [359133,1b90ec8923c8135d] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=1b90ec8923c8135d, body=] 2023-04-29T13:27:00.23647+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23652+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23654+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23655+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23657+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23658+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23659+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23661+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23662+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23663+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23665+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23666+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23667+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.2367+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23672+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23674+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23675+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23677+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23678+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23679+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23681+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23682+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23683+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23684+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23686+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23687+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23689+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.2369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23691+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23693+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23694+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23696+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23698+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23699+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.237+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23703+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23704+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23705+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23707+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23708+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23709+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23711+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23716+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.2372+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23727+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23739+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23745+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23746+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.2375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23753+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23754+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23758+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23759+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.2376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23762+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23778+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23781+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23822+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23827+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23829+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23841+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23844+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23845+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23847+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23852+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23854+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23855+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23857+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23858+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23859+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23862+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23863+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23865+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23866+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23867+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23869+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23874+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23876+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23877+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23878+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.2388+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23881+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.23884+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:00.23886+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:00.24084+08:00 INFO [359133,5395610411a127b2] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=5395610411a127b2, body=] 2023-04-29T13:27:00.24097+08:00 INFO [359133,2efbbe1e5cc205bf] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=2efbbe1e5cc205bf, body=] 2023-04-29T13:27:00.24181+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:27:00.24185+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:27:02.72702+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.670809ms 2023-04-29T13:27:02.72709+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:02.82545+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.836811ms 2023-04-29T13:27:02.82552+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:07.72635+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.339504ms 2023-04-29T13:27:07.72642+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:07.82452+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.544807ms 2023-04-29T13:27:07.82457+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:12.72791+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.491334ms 2023-04-29T13:27:12.72798+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:12.82529+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.138016ms 2023-04-29T13:27:12.82535+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:15.23532+08:00 INFO [359133,7bd914fe1850debe] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=7bd914fe1850debe, body=] 2023-04-29T13:27:15.23623+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23628+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.2363+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23631+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23633+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23634+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23635+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23637+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.2364+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23642+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23643+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23645+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23646+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23647+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23649+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.2365+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23651+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23652+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23654+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23655+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23656+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23658+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23659+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.2366+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23661+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23663+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23664+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23665+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23667+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23669+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23671+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23672+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23673+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23675+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23676+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23677+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23679+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.2368+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23681+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23683+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23684+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23685+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23687+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23688+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23689+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23691+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23692+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23693+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23696+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23697+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23699+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.237+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23701+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23702+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23704+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23737+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.2375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23756+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.2376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23762+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23778+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23834+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23839+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23841+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23842+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23849+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.2385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23853+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23857+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23861+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23862+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23865+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23866+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23867+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23869+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23871+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23872+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23874+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23875+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23876+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.23877+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23879+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:15.2388+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:15.23998+08:00 INFO [359133,63a20136be056a6b] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=63a20136be056a6b, body=] 2023-04-29T13:27:15.24011+08:00 INFO [359133,a55cee2e00d02368] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=a55cee2e00d02368, body=] 2023-04-29T13:27:15.24094+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:27:15.24098+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:27:17.72639+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.529307ms 2023-04-29T13:27:17.72646+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:17.82519+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.529007ms 2023-04-29T13:27:17.82526+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:22.73152+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.361076ms 2023-04-29T13:27:22.7316+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:22.8489+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=30.98664ms 2023-04-29T13:27:22.84897+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:27.7277+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.508221ms 2023-04-29T13:27:27.72777+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:27.82555+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.585508ms 2023-04-29T13:27:27.82561+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:30.23544+08:00 INFO [359133,44fe537bfe2925dd] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=44fe537bfe2925dd, body=] 2023-04-29T13:27:30.23562+08:00 INFO [359133,50b12923153bad89] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=50b12923153bad89, body=] 2023-04-29T13:27:30.23627+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:27:30.23631+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:27:30.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23739+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23754+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23756+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.2376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23761+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23765+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23773+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23777+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23781+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23782+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23784+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23785+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23786+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23793+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23796+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23798+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23801+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23815+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23817+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23827+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23828+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.2383+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23831+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23834+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23835+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23839+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23841+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23842+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23843+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23846+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23847+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23848+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.2385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23851+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23853+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23854+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23857+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23858+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.2386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23862+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23863+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23865+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23866+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23867+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23869+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.2387+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23871+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23873+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23874+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23875+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23877+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23878+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23879+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23882+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23884+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23886+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23887+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23889+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.2389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23891+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23893+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23894+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23896+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23897+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23898+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.239+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23901+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23956+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.2396+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23961+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23963+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23965+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23968+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.2397+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23973+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23976+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23977+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23978+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.2398+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23981+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23982+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23984+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23985+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23986+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23988+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23989+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.2399+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23992+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23993+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23994+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23995+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23997+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.23998+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.23999+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.24+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.24002+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.24003+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.24004+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:30.24007+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:30.24574+08:00 INFO [359133,f913e7dd37fc42a5] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=f913e7dd37fc42a5, body=] 2023-04-29T13:27:32.72627+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.458906ms 2023-04-29T13:27:32.72634+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:32.82485+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.546807ms 2023-04-29T13:27:32.82491+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:37.72849+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.657837ms 2023-04-29T13:27:37.72859+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:37.82745+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.579336ms 2023-04-29T13:27:37.82751+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:42.72704+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.639508ms 2023-04-29T13:27:42.72711+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:42.82506+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.862412ms 2023-04-29T13:27:42.82517+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:45.23624+08:00 INFO [359133,fcc1e29d9780ec67] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=fcc1e29d9780ec67, body=] 2023-04-29T13:27:45.23652+08:00 INFO [359133,4357e9a238602ddb] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=4357e9a238602ddb, body=] 2023-04-29T13:27:45.23738+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23746+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.2375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23754+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23759+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.2376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23761+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23765+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23767+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23768+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23769+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23772+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23776+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23777+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23778+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.2378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23786+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23787+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23788+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.2379+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23791+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23792+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23794+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23795+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23796+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23797+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23799+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.238+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23801+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23804+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23821+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23822+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23824+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23825+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23829+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.2383+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23832+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23833+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23839+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.2384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23846+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.2385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23857+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.2386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23864+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23865+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23867+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23868+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23869+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.2387+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23872+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23873+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23874+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23875+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23877+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23878+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23879+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23881+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23882+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23935+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23939+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23941+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23943+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23944+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23945+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23947+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23948+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23949+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23951+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23952+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23953+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23955+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23956+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23957+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23959+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.2396+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23961+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23962+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23964+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23965+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23966+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23968+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23969+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.2397+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23972+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23973+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23974+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23975+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.23977+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.23978+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:27:45.2398+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:27:45.24152+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:27:45.24157+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:27:45.24755+08:00 INFO [359133,f18940f34c59edb0] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=f18940f34c59edb0, body=] 2023-04-29T13:27:47.72631+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.781711ms 2023-04-29T13:27:47.72641+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:47.82596+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.593022ms 2023-04-29T13:27:47.82602+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:52.73495+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.902398ms 2023-04-29T13:27:52.73502+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:52.80188+08:00 WARN [359133,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 417211 fields:, error="open /proc/417211/status: no such file or directory" 2023-04-29T13:27:52.80196+08:00 WARN [359133,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 417232 fields: error="open /proc/417232/status: no such file or directory" 2023-04-29T13:27:52.82548+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.556721ms 2023-04-29T13:27:52.82555+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:57.72814+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.976128ms 2023-04-29T13:27:57.72821+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:27:57.82501+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.760111ms 2023-04-29T13:27:57.82508+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:00.23612+08:00 INFO [359133,5c6915a78e1f5593] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=5c6915a78e1f5593, body=] 2023-04-29T13:28:00.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23705+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23706+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23708+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23709+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.2371+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23712+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23713+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23714+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23716+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23717+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23718+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.2372+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23724+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23727+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23739+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23744+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23745+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23746+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23748+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23749+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.2375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23753+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23754+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23757+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23758+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23759+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.2376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23762+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23766+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23767+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23768+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23769+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23771+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23772+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23777+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23778+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23783+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23784+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23785+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23804+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23807+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23811+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23822+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23825+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23826+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23829+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23834+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23837+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.2384+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23841+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23843+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23846+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23847+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.2385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23851+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23853+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23854+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23855+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.2391+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23914+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23915+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23917+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23918+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23919+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23921+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23922+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23924+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23925+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23926+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23928+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23929+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.2393+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23931+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23933+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23934+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23935+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23936+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23939+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23941+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23942+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23943+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23945+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23946+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23948+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23949+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.2395+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23952+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23953+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.23954+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:00.23955+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:00.24074+08:00 INFO [359133,c32be3b5f85ba11f] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=c32be3b5f85ba11f, body=] 2023-04-29T13:28:00.24088+08:00 INFO [359133,a2f0f1ced9ed7896] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=a2f0f1ced9ed7896, body=] 2023-04-29T13:28:00.2434+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:28:00.24344+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:28:02.7263+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.590208ms 2023-04-29T13:28:02.72636+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:02.82502+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.050001ms 2023-04-29T13:28:02.82509+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:07.72652+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.872111ms 2023-04-29T13:28:07.7266+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:07.82941+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.708967ms 2023-04-29T13:28:07.82949+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:12.72703+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.790011ms 2023-04-29T13:28:12.72711+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:12.82586+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.161016ms 2023-04-29T13:28:12.82593+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:15.23648+08:00 INFO [359133,6918c4d14e9876be] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=6918c4d14e9876be, body=] 2023-04-29T13:28:15.23666+08:00 INFO [359133,07f83342a48eac85] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=07f83342a48eac85, body=] 2023-04-29T13:28:15.23723+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:28:15.23726+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:28:15.2382+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23824+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23829+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23832+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23833+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.2384+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23842+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23849+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.2385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23853+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23855+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23856+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23857+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23859+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23862+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23864+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23865+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23866+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23867+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23869+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.2387+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23871+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23873+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23874+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23875+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23876+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23878+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23879+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.2388+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23882+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23883+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23884+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23885+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23887+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23888+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23889+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.2389+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23892+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23893+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23894+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23895+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23897+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23898+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23901+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23902+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23903+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23905+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23906+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23907+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23909+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.2391+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23911+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23913+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23914+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23915+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23916+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23918+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23919+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23921+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23922+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23923+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23924+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23926+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23927+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23928+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.2393+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23931+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23932+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23933+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23935+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23936+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23939+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23941+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23942+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23944+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23945+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23947+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23948+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23949+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23951+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23952+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23953+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23954+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23956+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23957+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23959+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23961+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23962+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23963+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.23965+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.23966+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.24011+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.24014+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.24015+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.24017+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.24018+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.24019+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.24021+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.24023+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.24024+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.24026+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.24027+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.24028+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.2403+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.24031+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.24032+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.24034+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.24035+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.24037+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.2404+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.24041+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.24042+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.24044+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.24045+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.24046+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.24047+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.24049+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.2405+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.24051+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.24053+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.24054+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.24055+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:15.24056+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:15.24644+08:00 INFO [359133,145adc284223af02] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=145adc284223af02, body=] 2023-04-29T13:28:17.72686+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.74951ms 2023-04-29T13:28:17.72692+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:17.82549+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.989414ms 2023-04-29T13:28:17.82557+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:22.72823+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.897826ms 2023-04-29T13:28:22.7283+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:22.82664+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.218331ms 2023-04-29T13:28:22.82672+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:27.72683+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.576207ms 2023-04-29T13:28:27.72695+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:27.8288+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.408162ms 2023-04-29T13:28:27.82887+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:30.23701+08:00 INFO [359133,42d0bd396d63a6ed] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=42d0bd396d63a6ed, body=] 2023-04-29T13:28:30.23797+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23807+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23811+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23816+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23829+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23834+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23837+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.2384+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23841+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23844+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23845+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23846+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23848+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23849+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.2385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23852+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23853+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23856+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23857+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.2386+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23861+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23862+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23865+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23866+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23868+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23869+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23873+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23875+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23876+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23877+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23879+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.2388+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23881+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23883+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23884+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23885+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23887+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23888+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23889+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23894+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23896+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23898+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23899+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23902+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23903+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23904+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23906+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23907+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23908+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.2391+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23912+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23914+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23915+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23916+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23918+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23919+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.2392+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23922+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23923+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23924+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23926+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23928+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23929+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.2393+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23931+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23933+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23934+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23935+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23937+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23939+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23941+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23942+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23943+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23945+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23946+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.23948+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.23949+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.24+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.24003+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.24005+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.24006+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.24008+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.24009+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.2401+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.24012+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.24013+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.24015+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.24016+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.24017+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.24019+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.2402+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.24021+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.24022+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.24024+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.24026+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.24027+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.24028+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.24029+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.24031+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.24032+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.24033+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.24035+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.24036+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.24039+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.2404+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.24042+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.24043+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.24045+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:30.24046+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:30.24159+08:00 INFO [359133,9d5ca9c2d61d10a4] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=9d5ca9c2d61d10a4, body=] 2023-04-29T13:28:30.24173+08:00 INFO [359133,06128e32ea3c7868] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=06128e32ea3c7868, body=] 2023-04-29T13:28:30.24249+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:28:30.24252+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:28:32.7279+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.583421ms 2023-04-29T13:28:32.72801+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:32.82598+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.233417ms 2023-04-29T13:28:32.82605+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:37.72626+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.425906ms 2023-04-29T13:28:37.72633+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:37.82599+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.042814ms 2023-04-29T13:28:37.82606+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:42.72627+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.621408ms 2023-04-29T13:28:42.72634+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:42.82598+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.46842ms 2023-04-29T13:28:42.82605+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:45.23522+08:00 INFO [359133,8197eb9879d47dff] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=8197eb9879d47dff, body=] 2023-04-29T13:28:45.2364+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23646+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23648+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23649+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23652+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23654+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23655+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23656+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23658+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23659+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.2366+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23662+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23663+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23664+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23667+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23679+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23681+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23682+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23686+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23689+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.2369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23691+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23692+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23694+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23696+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23698+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23699+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.237+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23703+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23707+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23711+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23721+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23728+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23739+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23741+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23745+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23746+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23748+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23749+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.2375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.2376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23761+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23762+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23765+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23769+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23778+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23783+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23786+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23793+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23794+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23795+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23798+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23799+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23802+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23803+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23806+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23807+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.2381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23864+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23865+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23867+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23868+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23871+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23872+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23873+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23875+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23876+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23878+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23879+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.2388+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23882+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23883+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23889+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23891+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23892+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23893+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23895+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23896+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23897+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23899+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23901+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23902+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23904+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23905+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.23906+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:28:45.23907+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:28:45.24021+08:00 INFO [359133,d299bd39d8855c11] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=d299bd39d8855c11, body=] 2023-04-29T13:28:45.24034+08:00 INFO [359133,2e927a8e1f090745] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=2e927a8e1f090745, body=] 2023-04-29T13:28:45.24103+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:28:45.24107+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:28:47.7267+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.486606ms 2023-04-29T13:28:47.72679+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:47.82463+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.267203ms 2023-04-29T13:28:47.8247+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:52.755+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=28.081199ms 2023-04-29T13:28:52.75507+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:52.82513+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.167616ms 2023-04-29T13:28:52.8252+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:57.72671+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.669509ms 2023-04-29T13:28:57.72678+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:28:57.82525+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.948313ms 2023-04-29T13:28:57.82533+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:00.23593+08:00 INFO [359133,a310bcb73d744413] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=a310bcb73d744413, body=] 2023-04-29T13:29:00.23612+08:00 INFO [359133,bfd1ecab5a4c600a] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=bfd1ecab5a4c600a, body=] 2023-04-29T13:29:00.23671+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:29:00.23674+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:29:00.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23777+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23792+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23793+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23796+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23797+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.238+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23801+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23804+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23818+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23823+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23828+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.2383+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23835+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.2384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23846+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23849+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.2385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23853+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23857+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23861+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23862+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23864+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23866+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23867+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23869+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23871+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23874+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23876+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23878+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23879+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.2388+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23881+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23883+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23884+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23886+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23887+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23888+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.2389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23891+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23893+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23896+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23898+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23899+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23902+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23903+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23904+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23905+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23907+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23908+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.2391+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23911+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23912+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23914+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23916+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23918+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.2392+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23921+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23922+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23924+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23925+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23926+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23928+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23929+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.2393+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23931+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23933+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23934+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23936+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23937+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23994+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.23998+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.23999+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.24002+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.24006+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.24007+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.24009+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.2401+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.24011+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.24013+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.24014+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.24015+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.24017+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.24018+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.24019+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.2402+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.24022+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.24023+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.24024+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.24026+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.24027+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.24029+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.2403+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.24031+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.24033+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.24034+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.24036+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.24037+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.2404+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.24041+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.24043+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:00.24044+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:00.24572+08:00 INFO [359133,1188d334fa56781d] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=1188d334fa56781d, body=] 2023-04-29T13:29:02.72698+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.233117ms 2023-04-29T13:29:02.72705+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:02.8264+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.787825ms 2023-04-29T13:29:02.82647+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:07.72658+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.473506ms 2023-04-29T13:29:07.72664+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:07.82588+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.297818ms 2023-04-29T13:29:07.82595+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:12.72889+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.207545ms 2023-04-29T13:29:12.72899+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:12.82626+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.665524ms 2023-04-29T13:29:12.82639+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:15.23526+08:00 INFO [359133,9f72ff3f6351d769] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=9f72ff3f6351d769, body=] 2023-04-29T13:29:15.23553+08:00 INFO [359133,6b82aab24b1a64a2] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=6b82aab24b1a64a2, body=] 2023-04-29T13:29:15.23621+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:29:15.23625+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:29:15.23811+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23826+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23834+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23844+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23846+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23847+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23848+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.2385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23851+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23856+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23857+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23859+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.2386+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23862+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23863+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23864+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23866+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23869+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23871+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23874+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23876+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23878+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.2388+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23881+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23883+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23885+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23886+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23888+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23889+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.2389+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23892+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23893+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23894+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23896+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23897+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23899+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23902+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23903+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23904+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23906+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23907+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23908+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.2391+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23917+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23919+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23921+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23922+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.23924+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.23925+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24032+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24041+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24042+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24044+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24045+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24047+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24048+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.2405+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24052+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24053+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24055+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24056+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24057+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.2406+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24061+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24063+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24064+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24066+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24067+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24068+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.2407+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24071+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24072+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24074+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24075+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24077+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24078+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24079+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24081+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24082+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24084+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24085+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24086+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24088+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24089+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24091+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24092+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24093+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24095+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24096+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24097+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24154+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24158+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.2416+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24161+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24162+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24164+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24165+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24166+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24168+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24169+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24171+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24172+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24173+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24177+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24178+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.2418+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24181+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24183+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24184+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24185+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24187+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24188+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24189+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24191+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24192+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24193+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24195+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24196+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24197+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24199+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.242+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:15.24201+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:15.24824+08:00 INFO [359133,49228ec8822be26f] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=49228ec8822be26f, body=] 2023-04-29T13:29:17.72685+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.807211ms 2023-04-29T13:29:17.72692+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:17.82931+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.97237ms 2023-04-29T13:29:17.82941+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:22.7344+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.387919ms 2023-04-29T13:29:22.73448+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:22.82571+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.040915ms 2023-04-29T13:29:22.82578+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:27.72608+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.499406ms 2023-04-29T13:29:27.72616+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:27.83346+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.715523ms 2023-04-29T13:29:27.83354+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:30.23815+08:00 INFO [359133,a336f22ec01e9009] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=a336f22ec01e9009, body=] 2023-04-29T13:29:30.23911+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23916+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23918+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23919+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23921+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23922+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23923+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23924+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23931+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23933+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23935+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23936+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23939+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.2394+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23942+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23943+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23944+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23946+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23947+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23948+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.2395+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23951+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23952+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23954+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23955+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23956+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23958+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.2396+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23961+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23962+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23964+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23965+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23966+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23967+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23969+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.2397+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23972+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23973+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23976+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23977+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23978+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23979+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23981+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23982+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23983+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23985+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23986+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23987+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23988+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.2399+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23991+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23992+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23993+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23995+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23996+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.23997+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.23998+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24001+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24002+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24004+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24005+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24006+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24007+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24009+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.2401+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24011+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24013+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24015+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24016+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24017+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24018+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.2402+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24021+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24022+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24025+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24026+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24031+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24033+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24034+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24035+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24036+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24042+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24044+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24045+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24046+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24048+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24049+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24051+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24052+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24053+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24054+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24056+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24057+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24058+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.2406+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24061+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24062+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24064+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24065+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24066+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24067+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24113+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24116+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24117+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24118+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.2412+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24121+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24123+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24124+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24125+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24126+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24132+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24134+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24135+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24138+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.2414+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24141+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24143+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24144+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24145+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24146+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24148+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24149+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.2415+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24153+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24154+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24155+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24157+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24158+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24159+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.2416+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24162+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:30.24163+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:30.24271+08:00 INFO [359133,655b9168d7104508] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=655b9168d7104508, body=] 2023-04-29T13:29:30.24283+08:00 INFO [359133,d9b4bdf4b102befe] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=d9b4bdf4b102befe, body=] 2023-04-29T13:29:30.24355+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:29:30.24359+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:29:32.72709+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.874511ms 2023-04-29T13:29:32.72716+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:32.82496+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.309404ms 2023-04-29T13:29:32.82502+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:37.72682+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.845611ms 2023-04-29T13:29:37.72689+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:37.82649+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.637422ms 2023-04-29T13:29:37.82657+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:42.73439+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=14.650808ms 2023-04-29T13:29:42.73446+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:42.8254+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.71801ms 2023-04-29T13:29:42.82547+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:45.23494+08:00 INFO [359133,6bce46c764422467] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=6bce46c764422467, body=] 2023-04-29T13:29:45.23601+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23606+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23608+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.2361+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23611+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23613+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23614+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23615+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23617+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23619+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.2362+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23622+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23623+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23624+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23625+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23627+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23628+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23629+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23631+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23632+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23634+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23636+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23638+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.2364+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23641+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23643+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23645+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23646+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23648+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23649+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23651+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23653+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23654+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23655+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23657+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23658+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23659+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.2366+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23662+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.2367+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23671+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23672+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23674+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23675+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23676+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23678+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23679+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.2368+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23682+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23683+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23684+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23685+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23687+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23688+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23689+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23691+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23692+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23694+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23696+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23697+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23699+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.237+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23706+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23707+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23711+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23715+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23721+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23722+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.2373+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23733+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23734+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23736+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23738+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.2374+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23741+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23744+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.2381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23811+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23813+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23825+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.2385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23853+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23856+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23857+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23872+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23874+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23875+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23877+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23878+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23879+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23881+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23882+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23883+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23884+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23886+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23887+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.2389+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23892+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.23893+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:29:45.23894+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:29:45.24026+08:00 INFO [359133,c0ab8a2ee1a1cf1e] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=c0ab8a2ee1a1cf1e, body=] 2023-04-29T13:29:45.24041+08:00 INFO [359133,698966c67eac8160] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=698966c67eac8160, body=] 2023-04-29T13:29:45.24294+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:29:45.24298+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:29:47.72591+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.253203ms 2023-04-29T13:29:47.72598+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:47.82527+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.615209ms 2023-04-29T13:29:47.82533+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:52.73918+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.14573ms 2023-04-29T13:29:52.73925+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:52.81302+08:00 WARN [359133,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 427322 fields: error="open /proc/427322/status: no such file or directory" 2023-04-29T13:29:52.8131+08:00 WARN [359133,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 427343 fields:, error="open /proc/427343/status: no such file or directory" 2023-04-29T13:29:52.82963+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.70168ms 2023-04-29T13:29:52.82971+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:57.72633+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.842411ms 2023-04-29T13:29:57.72642+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:29:57.825+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.615109ms 2023-04-29T13:29:57.82506+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:00.2352+08:00 INFO [359133,4a6a2a0388545277] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=4a6a2a0388545277, body=] 2023-04-29T13:30:00.23615+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23619+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23621+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23623+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23624+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23625+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23627+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23628+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.2363+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23632+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23633+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23634+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23636+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23639+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.2364+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23642+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23643+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23645+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23646+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23647+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23649+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.2365+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23651+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23655+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23664+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23665+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23666+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23669+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.2367+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23672+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23673+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23675+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23676+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23677+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23679+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.2368+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23681+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23683+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23684+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23685+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23687+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23688+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23689+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23692+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23694+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23695+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23696+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23698+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23699+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23702+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23707+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23711+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23712+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23715+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23716+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23717+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23719+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.2372+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23723+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23724+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23725+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23727+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23728+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23729+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23732+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23733+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23734+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23736+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23739+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.2374+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23744+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23745+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23747+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23748+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23749+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.2375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23752+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23753+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23756+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23761+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23765+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23766+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23767+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23769+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.2377+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23771+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23772+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23774+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23775+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23776+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23778+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23833+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23839+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.2384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23844+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23846+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23847+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23848+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.2385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23851+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23852+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23854+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23855+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23856+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23864+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23867+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23868+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.2387+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23871+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23873+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23874+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23875+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23877+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23878+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23879+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.23881+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:00.23882+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:00.24013+08:00 INFO [359133,f38557d8d834fd26] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=f38557d8d834fd26, body=] 2023-04-29T13:30:00.24028+08:00 INFO [359133,36d0a008fca6f2ce] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=36d0a008fca6f2ce, body=] 2023-04-29T13:30:00.24107+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:30:00.24111+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:30:02.72614+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.383405ms 2023-04-29T13:30:02.72621+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:02.82502+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.252903ms 2023-04-29T13:30:02.82509+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:07.72649+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.74711ms 2023-04-29T13:30:07.72656+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:07.82617+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.403019ms 2023-04-29T13:30:07.82624+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:12.72704+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.368919ms 2023-04-29T13:30:12.72711+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:12.82557+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.889112ms 2023-04-29T13:30:12.82564+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:15.23521+08:00 INFO [359133,a90b6421089950be] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=a90b6421089950be, body=] 2023-04-29T13:30:15.23618+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23623+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23625+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23627+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23628+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.2363+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23632+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23633+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23635+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23636+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23641+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23643+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23644+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23646+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23647+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23649+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.2365+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23651+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23653+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23655+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23656+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23658+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23659+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.2366+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23662+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23663+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23664+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23666+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23667+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.2367+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23671+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23672+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23673+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23675+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23676+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23677+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23679+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.2368+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23681+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23683+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23684+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23685+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23687+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23692+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23694+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23695+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23697+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23698+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23699+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23701+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23702+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23704+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23705+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23706+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23708+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23709+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.2371+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23712+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23713+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23714+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23716+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23717+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23719+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.2372+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23723+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23724+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23725+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23728+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23729+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23732+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23733+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23736+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23746+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23749+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.2375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23753+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23754+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23756+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23757+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23758+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.2376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23761+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23762+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23765+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23766+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23767+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23769+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.2377+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23771+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23772+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23833+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23841+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23853+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23857+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.2386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23862+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23864+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23866+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23867+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23868+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23872+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23874+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23875+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23876+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.23878+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:15.23879+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:15.24002+08:00 INFO [359133,0db860c45aa83b57] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=0db860c45aa83b57, body=] 2023-04-29T13:30:15.24014+08:00 INFO [359133,4f0bffece2e5f65f] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=4f0bffece2e5f65f, body=] 2023-04-29T13:30:15.24098+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:30:15.24102+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:30:17.72715+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.73451ms 2023-04-29T13:30:17.72723+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:17.82515+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.331304ms 2023-04-29T13:30:17.82526+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:22.72822+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.332832ms 2023-04-29T13:30:22.72831+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:22.82511+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.426306ms 2023-04-29T13:30:22.82518+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:27.72669+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.533707ms 2023-04-29T13:30:27.72678+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:27.8245+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.100101ms 2023-04-29T13:30:27.82456+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:30.23535+08:00 INFO [359133,6d46c78647751122] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=6d46c78647751122, body=] 2023-04-29T13:30:30.23558+08:00 INFO [359133,8f8613735b062135] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=8f8613735b062135, body=] 2023-04-29T13:30:30.23935+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.23941+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.23944+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.23945+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.23947+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.23949+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.2395+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.23952+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.23954+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.23955+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.23958+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.23959+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.23961+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.23963+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.23965+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.23966+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.23968+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.2397+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.23972+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.23973+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.23975+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.23976+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.23978+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.23979+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.23981+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.23983+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.23985+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.23986+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.23988+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.23989+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.23991+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.23992+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.23994+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.23995+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.23997+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.23998+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24002+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24006+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24009+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24011+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24013+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24014+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24016+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24018+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24019+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24021+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24023+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24028+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24031+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24032+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24034+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24035+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24037+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24043+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24045+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24047+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24048+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.2405+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24051+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24053+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24054+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24058+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24059+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24061+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24063+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24066+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24067+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24069+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.2407+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24072+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24073+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24076+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24077+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.2408+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24081+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24083+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24084+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24086+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24088+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.2409+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24091+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24093+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24094+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24096+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24097+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24099+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.241+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24102+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24103+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24105+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24106+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24108+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24109+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24113+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24115+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24116+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24118+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.2412+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24122+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24126+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24129+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24314+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24318+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.2432+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24322+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24323+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24332+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24334+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24336+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24339+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.2434+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24342+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24343+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24346+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24348+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.2435+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24352+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24354+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24355+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24357+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24359+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24361+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24362+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24364+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24365+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24367+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24368+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.2437+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24371+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24373+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:30.24378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:30.24572+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:30:30.24576+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:30:30.25223+08:00 INFO [359133,cfb50b551a987edd] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=cfb50b551a987edd, body=] 2023-04-29T13:30:32.72603+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.507707ms 2023-04-29T13:30:32.72609+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:32.82501+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.308904ms 2023-04-29T13:30:32.82507+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:37.7271+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.786511ms 2023-04-29T13:30:37.72716+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:37.82461+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.437706ms 2023-04-29T13:30:37.82467+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:42.72673+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.267604ms 2023-04-29T13:30:42.7268+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:42.8247+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.530007ms 2023-04-29T13:30:42.82479+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:45.23513+08:00 INFO [359133,a02a76ec7a2f6e97] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=a02a76ec7a2f6e97, body=] 2023-04-29T13:30:45.23611+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23615+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23617+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23618+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23619+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23621+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23622+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23623+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23625+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23626+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23627+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23629+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23631+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23632+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23633+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23636+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23638+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.2364+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23641+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23643+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23644+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23645+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23646+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23648+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23649+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.2365+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23652+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23653+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23654+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23656+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23657+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23658+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23659+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23661+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23662+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23663+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23664+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23666+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23667+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23669+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.2367+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23672+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23673+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23675+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23676+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23677+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23679+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23684+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23686+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23687+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23688+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.2369+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23691+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23692+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23693+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23695+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23696+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23697+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23701+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23706+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23707+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.2371+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23711+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23715+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23721+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23727+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23729+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.2373+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23733+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23734+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23739+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23741+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23745+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23746+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.2375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23754+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23759+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23816+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23817+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23818+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23826+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23832+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23833+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23839+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.2384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23841+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.2385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:30:45.23853+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:30:45.23968+08:00 INFO [359133,0b73b22ffdb1c20b] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=0b73b22ffdb1c20b, body=] 2023-04-29T13:30:45.24143+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:30:45.24158+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:30:45.24231+08:00 INFO [359133,a286d29a7c6cb864] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=a286d29a7c6cb864, body=] 2023-04-29T13:30:47.72675+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.469106ms 2023-04-29T13:30:47.72682+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:47.82448+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.0589ms 2023-04-29T13:30:47.82455+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:52.75647+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.428062ms 2023-04-29T13:30:52.75661+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:52.82504+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.557107ms 2023-04-29T13:30:52.82511+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:57.72607+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.247403ms 2023-04-29T13:30:57.72614+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:30:57.82475+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.072901ms 2023-04-29T13:30:57.82482+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:00.23679+08:00 INFO [359133,9cbb2bda976b2297] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=9cbb2bda976b2297, body=] 2023-04-29T13:31:00.2396+08:00 INFO [359133,39a060160f843eca] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=39a060160f843eca, body=] 2023-04-29T13:31:00.24019+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:31:00.24022+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:31:00.24572+08:00 INFO [359133,51670472e23d722d] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=51670472e23d722d, body=] 2023-04-29T13:31:00.25108+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25114+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25117+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25118+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25122+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25123+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25125+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25126+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25129+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25131+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25132+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25134+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25137+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25139+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25141+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25143+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25144+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25146+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25147+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25149+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.2515+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25153+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25154+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25156+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25157+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25159+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.2516+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25162+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25164+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25168+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25171+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25172+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25174+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25175+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25177+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25179+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.2518+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25182+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25184+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25185+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25188+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25189+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25191+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25192+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25194+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25195+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25197+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25198+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.252+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25201+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25203+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25205+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25206+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25208+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25209+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.2521+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25212+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25214+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25215+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25218+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25219+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25221+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25222+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25224+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25226+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25227+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25229+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.2523+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25232+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25234+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25236+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25241+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25243+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25244+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25246+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25247+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25249+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25251+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25253+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25254+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25256+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25257+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25259+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25261+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25262+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25264+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.2527+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25272+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25274+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25275+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25277+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25278+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.2528+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25281+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25283+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25285+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25287+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25288+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.2529+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25292+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25293+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25339+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25342+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25344+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25345+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25347+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25349+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25351+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25352+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25353+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25355+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25356+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25357+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25359+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.2536+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25361+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25362+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25364+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.2537+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25371+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25373+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25377+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.2538+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25384+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:00.25386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:00.25388+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:02.72571+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.165902ms 2023-04-29T13:31:02.72578+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:02.82463+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.382105ms 2023-04-29T13:31:02.82473+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:07.72841+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.055143ms 2023-04-29T13:31:07.72848+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:07.82544+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.212717ms 2023-04-29T13:31:07.82552+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:12.72916+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.415648ms 2023-04-29T13:31:12.72922+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:12.82665+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.050328ms 2023-04-29T13:31:12.82671+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:15.23522+08:00 INFO [359133,41a50b7fdc0a5ba4] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=41a50b7fdc0a5ba4, body=] 2023-04-29T13:31:15.23608+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:31:15.23613+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:31:15.24281+08:00 INFO [359133,40ad7f39f8717c50] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=40ad7f39f8717c50, body=] 2023-04-29T13:31:15.243+08:00 INFO [359133,e5ce65dae5e22915] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=e5ce65dae5e22915, body=] 2023-04-29T13:31:15.24439+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24443+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24448+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.2445+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24451+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24452+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24454+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24455+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24456+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24458+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24459+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24461+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24464+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24465+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24466+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24468+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24469+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.2447+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24472+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24473+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24474+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24476+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24477+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24478+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.2448+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24481+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24487+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24489+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24495+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24497+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24499+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.245+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24501+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24506+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24508+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24509+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24511+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24512+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24513+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24514+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.2452+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24521+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24523+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24524+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24525+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24526+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24528+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24529+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24535+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24536+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24539+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24541+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24547+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24549+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.2455+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24551+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24558+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24561+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24562+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24563+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24564+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24566+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24567+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24568+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24574+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24575+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24578+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.2458+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24581+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24588+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24591+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24597+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24599+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.246+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24601+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24603+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24604+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24607+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24609+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.2461+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24611+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24613+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24614+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24615+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24617+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24622+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24623+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24624+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.2463+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24631+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24632+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24634+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24635+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24636+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24639+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24645+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24647+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24649+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.2465+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24651+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24653+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24659+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.2472+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24727+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24729+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.2473+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24734+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24745+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24746+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.2475+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24758+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24759+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24761+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24762+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24768+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24773+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24781+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:15.24793+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:15.24795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:17.7275+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.066015ms 2023-04-29T13:31:17.72758+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:17.82472+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.602608ms 2023-04-29T13:31:17.82478+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:22.72658+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.332605ms 2023-04-29T13:31:22.72665+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:22.82393+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.868997ms 2023-04-29T13:31:22.82399+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:27.72617+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.268504ms 2023-04-29T13:31:27.72623+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:27.8249+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.247803ms 2023-04-29T13:31:27.82497+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:30.23551+08:00 INFO [359133,a0678d4ab2fb6b44] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=a0678d4ab2fb6b44, body=] 2023-04-29T13:31:30.23631+08:00 INFO [359133,2ca443361469f86f] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=2ca443361469f86f, body=] 2023-04-29T13:31:30.23917+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.23922+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.23924+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.23926+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.23928+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.23929+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.23931+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.23932+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.23934+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.23935+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.23938+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.2394+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.23942+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.23943+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.23945+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.23946+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.23948+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.2395+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.23951+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.23953+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.23954+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.23957+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.23958+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.2396+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.23962+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.23964+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.23965+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.23967+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.23968+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.2397+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.23972+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.23973+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.23975+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.23977+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.23978+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.2398+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.23981+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.23983+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.23985+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.23987+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.23988+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.23989+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.23992+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.23993+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.23995+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.23996+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.23998+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.23999+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24001+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24008+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.2401+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24012+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24013+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24015+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24016+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24018+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.2402+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24021+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24023+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24024+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24026+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24027+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24029+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24031+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24032+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24034+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24036+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24038+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.2404+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24042+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24043+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24045+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24047+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24048+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24049+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24051+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24052+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24056+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24058+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24059+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24061+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24063+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24064+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24066+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24068+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.2407+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24071+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24073+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24075+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24076+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24078+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24079+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24081+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24082+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24084+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24085+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24087+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24089+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.2409+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24092+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24093+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24095+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24277+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24282+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24285+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24286+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24288+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24291+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24292+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24294+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24295+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24297+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24298+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.243+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24301+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24303+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.2431+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24312+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24313+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24315+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24316+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24318+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.2432+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24322+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24323+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24325+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24326+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24328+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24329+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24331+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24333+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.24334+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24337+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:30.2434+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:30.24434+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:31:30.24438+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:31:30.24509+08:00 INFO [359133,25756c61ee7217da] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=25756c61ee7217da, body=] 2023-04-29T13:31:32.72792+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.760824ms 2023-04-29T13:31:32.72798+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:32.83004+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.925584ms 2023-04-29T13:31:32.83012+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:37.72696+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.526907ms 2023-04-29T13:31:37.72703+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:37.82548+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.541507ms 2023-04-29T13:31:37.82554+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:42.72602+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.399305ms 2023-04-29T13:31:42.72608+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:42.82454+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.115102ms 2023-04-29T13:31:42.82468+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:45.2352+08:00 INFO [359133,be0bd9dd6dc9daac] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=be0bd9dd6dc9daac, body=] 2023-04-29T13:31:45.23543+08:00 INFO [359133,43af445ffcdb6b90] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=43af445ffcdb6b90, body=] 2023-04-29T13:31:45.23612+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:31:45.23616+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:31:45.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23722+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23723+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23738+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23754+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23756+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23757+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23758+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23769+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23771+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23772+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23775+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23776+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23777+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23779+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.2378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23786+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23815+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23817+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23818+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23819+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23826+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23829+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23832+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23833+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23839+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.2384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.2385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23853+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23864+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23866+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23867+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23868+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.2387+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23871+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23872+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23873+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23919+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23922+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23924+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23925+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23926+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23927+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23929+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.2393+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23932+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23933+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23934+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23936+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23938+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.2394+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23941+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23943+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23944+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23945+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23947+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23948+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23949+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23951+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23953+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23954+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23955+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23956+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23958+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23959+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.2396+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23966+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.23967+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:31:45.23969+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:31:45.24759+08:00 INFO [359133,58c1bddb2775940c] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=58c1bddb2775940c, body=] 2023-04-29T13:31:47.72553+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.178102ms 2023-04-29T13:31:47.7256+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:47.82545+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.288417ms 2023-04-29T13:31:47.82551+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:52.75432+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=33.670478ms 2023-04-29T13:31:52.7544+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:52.82426+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.342804ms 2023-04-29T13:31:52.82433+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:57.72639+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.491006ms 2023-04-29T13:31:57.72646+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:31:57.82558+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.624008ms 2023-04-29T13:31:57.82565+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:00.23495+08:00 INFO [359133,7a57ade7b187fab4] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=7a57ade7b187fab4, body=] 2023-04-29T13:32:00.23514+08:00 INFO [359133,cfaa48a3bce8604e] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=cfaa48a3bce8604e, body=] 2023-04-29T13:32:00.23578+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:32:00.23581+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:32:00.23673+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23677+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23678+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.2368+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23681+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23683+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23684+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23686+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23687+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23688+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23689+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23691+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23692+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23693+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23696+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23697+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23698+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.237+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23701+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23703+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23711+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23715+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23721+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23722+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23736+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23739+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23743+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23747+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.2376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23762+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23769+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23778+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23783+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23784+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23786+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23789+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23793+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.2381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23812+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23813+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23866+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23872+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23874+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23876+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23877+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23879+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.2388+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23881+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23884+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23886+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23887+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23888+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.2389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23891+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23892+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23893+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23895+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23898+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23903+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23905+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23906+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23908+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23909+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.2391+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23911+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23913+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23914+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23915+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23917+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.23918+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:00.23919+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:00.24867+08:00 INFO [359133,8739247807773d6b] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=8739247807773d6b, body=] 2023-04-29T13:32:02.72662+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.242303ms 2023-04-29T13:32:02.72668+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:02.82477+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.657109ms 2023-04-29T13:32:02.82483+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:07.72658+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.676709ms 2023-04-29T13:32:07.72664+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:07.82733+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.491434ms 2023-04-29T13:32:07.82742+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:12.72767+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.42162ms 2023-04-29T13:32:12.72774+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:12.82455+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.386605ms 2023-04-29T13:32:12.82461+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:15.23508+08:00 INFO [359133,6fe4ca3a64cd5e45] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=6fe4ca3a64cd5e45, body=] 2023-04-29T13:32:15.23558+08:00 INFO [359133,031e23f9502a52c0] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=031e23f9502a52c0, body=] 2023-04-29T13:32:15.23624+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:32:15.23627+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:32:15.23743+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23747+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23759+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.2376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23761+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23766+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23769+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.2377+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23773+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23774+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23777+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23783+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23784+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23786+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23806+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.2381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23812+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23813+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23815+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23816+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23819+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.2382+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23829+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23832+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23833+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23839+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.2384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.2385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23853+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23857+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.2386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23864+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23865+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23866+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23868+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23869+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23872+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23873+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23874+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23876+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23877+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23879+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.2388+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23881+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23883+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23884+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23885+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23886+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23888+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23889+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23943+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23946+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23948+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23949+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23951+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23952+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23953+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23955+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23956+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23958+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23959+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.2396+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23962+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23963+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23965+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23966+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23967+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23969+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.2397+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23971+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23973+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23974+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23975+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23977+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23978+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23979+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23981+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23983+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23985+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23986+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.23987+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:15.23988+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:15.24512+08:00 INFO [359133,38d9cf3d20122927] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=38d9cf3d20122927, body=] 2023-04-29T13:32:17.72672+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.617008ms 2023-04-29T13:32:17.72678+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:17.83049+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.427562ms 2023-04-29T13:32:17.83055+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:22.72641+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.410606ms 2023-04-29T13:32:22.72648+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:22.82514+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.251603ms 2023-04-29T13:32:22.8252+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:27.72658+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.661209ms 2023-04-29T13:32:27.72666+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:27.82447+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.373804ms 2023-04-29T13:32:27.82453+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:30.23568+08:00 INFO [359133,6e48a1c7f461ba14] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=6e48a1c7f461ba14, body=] 2023-04-29T13:32:30.23587+08:00 INFO [359133,448df05284a77100] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=448df05284a77100, body=] 2023-04-29T13:32:30.23651+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:32:30.23656+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:32:30.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23758+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23759+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.2376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23762+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23765+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23766+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23767+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23769+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.2377+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23771+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23773+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23774+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23775+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23776+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23778+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23779+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.2378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23783+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23787+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23788+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23791+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23792+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23793+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23796+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23797+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.238+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23801+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23815+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23817+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23822+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23826+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23834+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23837+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23839+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.2384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23846+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.2385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23857+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23861+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23862+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23865+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23866+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23867+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23869+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23871+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23873+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23874+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23875+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23877+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23878+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23879+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.2388+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23882+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23883+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23884+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23886+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23936+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23941+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23942+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23944+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23945+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23946+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23948+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23949+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.2395+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23952+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23953+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23955+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23956+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23958+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.2396+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23961+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23962+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23964+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23965+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23966+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23968+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23969+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.2397+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23971+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23973+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23974+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23975+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23977+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23978+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23979+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.23981+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:30.23982+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:30.24594+08:00 INFO [359133,99db6c400c11fe7d] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=99db6c400c11fe7d, body=] 2023-04-29T13:32:32.72685+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.554108ms 2023-04-29T13:32:32.72691+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:32.82473+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.191602ms 2023-04-29T13:32:32.82479+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:37.72665+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.667609ms 2023-04-29T13:32:37.72673+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:37.82514+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.647709ms 2023-04-29T13:32:37.8252+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:42.72663+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.250817ms 2023-04-29T13:32:42.7267+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:42.82547+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.168116ms 2023-04-29T13:32:42.82554+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:45.23609+08:00 INFO [359133,bff8207bef2fdbaa] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=bff8207bef2fdbaa, body=] 2023-04-29T13:32:45.23638+08:00 INFO [359133,1b8c4bc04d7db707] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=1b8c4bc04d7db707, body=] 2023-04-29T13:32:45.23706+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:32:45.2371+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:32:45.23812+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.2382+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23823+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23824+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23829+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23832+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23833+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23839+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.2384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23853+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23857+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.2386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23864+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23865+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23867+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23868+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23869+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.2387+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23872+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23873+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23875+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23876+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23877+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23879+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.2388+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23881+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23884+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23885+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23886+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23888+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23893+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23894+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23896+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23897+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23898+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.239+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23901+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23902+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23903+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23905+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23906+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23907+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23908+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.2391+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23911+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23912+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23914+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23915+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23916+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23918+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23919+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23921+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23922+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23924+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23925+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23926+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23928+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23929+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.2393+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23931+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23933+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23934+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23935+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23937+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.2394+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23941+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23943+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23944+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23945+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23947+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23948+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23949+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.2395+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23952+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23953+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23954+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23955+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23957+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23958+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.23959+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.23961+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.24015+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.24019+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.2402+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.24022+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.24023+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.24025+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.24026+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.24028+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.24029+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.2403+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.24032+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.24033+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.24034+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.24035+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.24037+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.24039+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.24041+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.24042+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.24043+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.24045+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.24046+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.24048+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.24049+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.2405+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.24051+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.24053+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.24054+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.24055+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.24056+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.24058+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.24059+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:32:45.2406+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:32:45.24671+08:00 INFO [359133,9e6101897e95f27e] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=9e6101897e95f27e, body=] 2023-04-29T13:32:47.72662+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.71771ms 2023-04-29T13:32:47.72671+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:47.82545+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.053715ms 2023-04-29T13:32:47.82551+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:52.75285+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.445806ms 2023-04-29T13:32:52.75291+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:52.82489+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.559008ms 2023-04-29T13:32:52.82495+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:57.72684+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.218118ms 2023-04-29T13:32:57.72691+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:32:57.82509+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.481807ms 2023-04-29T13:32:57.82518+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:00.23559+08:00 INFO [359133,96bb95e4b75cd018] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=96bb95e4b75cd018, body=] 2023-04-29T13:33:00.23647+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23651+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23653+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23655+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23656+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23657+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23659+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23661+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23662+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23664+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23665+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23666+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23668+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23669+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.2367+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23671+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23673+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23674+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23675+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23677+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23678+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23679+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23681+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23682+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23683+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23684+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23686+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23687+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23688+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.2369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23691+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23692+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23694+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23696+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23697+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23699+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.237+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23701+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23702+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23704+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23705+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23706+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23708+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23709+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.2371+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23712+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23713+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23714+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23716+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23717+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23718+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23725+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23727+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23728+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23729+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23732+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23736+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23739+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23743+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23765+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23777+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23778+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23786+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23788+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23792+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23793+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23851+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23855+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23856+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23858+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23859+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23864+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23865+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23866+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23868+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23869+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23871+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23872+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23873+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23874+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23876+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23877+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23879+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.2388+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23881+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23882+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23884+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23885+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23886+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23888+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23889+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.2389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23891+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23893+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.23894+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:00.23895+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:00.2402+08:00 INFO [359133,29a70a4953445fad] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=29a70a4953445fad, body=] 2023-04-29T13:33:00.24037+08:00 INFO [359133,dcfe3f08299a3ff1] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=dcfe3f08299a3ff1, body=] 2023-04-29T13:33:00.24169+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:33:00.24173+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:33:02.7289+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.319948ms 2023-04-29T13:33:02.72898+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:02.82513+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.707111ms 2023-04-29T13:33:02.82522+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:07.72609+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.706511ms 2023-04-29T13:33:07.72615+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:07.83095+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.102688ms 2023-04-29T13:33:07.83104+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:12.72728+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.868114ms 2023-04-29T13:33:12.72735+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:12.82445+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.477407ms 2023-04-29T13:33:12.8245+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:15.23498+08:00 INFO [359133,3947c6c7c6f46239] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=3947c6c7c6f46239, body=] 2023-04-29T13:33:15.23588+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23594+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23596+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23598+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.236+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23601+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23602+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23604+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23605+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23606+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23608+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23609+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.2361+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23612+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23613+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23615+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23616+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23617+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23619+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.2362+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23622+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23624+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23626+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23627+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23628+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.2363+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23631+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23632+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23634+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23636+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23642+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23645+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23646+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23648+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23649+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.2365+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23652+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23654+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23663+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23664+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23666+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23667+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23668+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.2367+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23671+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23672+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23673+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23675+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23676+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23677+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23678+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.2368+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23681+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23683+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23684+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23685+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23687+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23688+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23689+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23691+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23692+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23693+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23694+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23696+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23697+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23698+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23701+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23711+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23715+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23718+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23719+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.2372+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23722+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23723+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23752+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23756+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.2376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23762+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23826+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23844+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23846+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23847+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23848+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.2385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23851+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23852+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23854+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23855+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23856+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23857+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23859+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23863+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23865+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23866+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23867+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23868+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.2387+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23871+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23872+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23874+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23875+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:15.23876+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:15.23993+08:00 INFO [359133,3742969c65a419cf] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=3742969c65a419cf, body=] 2023-04-29T13:33:15.24005+08:00 INFO [359133,704e6128c1f693b0] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=704e6128c1f693b0, body=] 2023-04-29T13:33:15.24075+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:33:15.24078+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:33:17.72806+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.200332ms 2023-04-29T13:33:17.72813+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:17.82601+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.230219ms 2023-04-29T13:33:17.82607+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:22.72588+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.534608ms 2023-04-29T13:33:22.72594+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:22.82588+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.879413ms 2023-04-29T13:33:22.82594+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:27.72675+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.508608ms 2023-04-29T13:33:27.72681+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:27.82572+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.159117ms 2023-04-29T13:33:27.82585+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:30.2351+08:00 INFO [359133,8cbdb00a551c80e5] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=8cbdb00a551c80e5, body=] 2023-04-29T13:33:30.23558+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23562+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23568+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.2357+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23576+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23577+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23582+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23583+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23585+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23586+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23588+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23589+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23596+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23597+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23598+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.236+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23601+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23606+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23608+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23609+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23615+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23619+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23621+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23622+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23627+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23629+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23635+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23639+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23641+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23642+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23643+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23645+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23786+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23789+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23793+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23816+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23822+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23824+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23834+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23837+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23841+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23842+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23843+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23846+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23853+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23854+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23857+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.2386+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23861+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23862+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23864+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23865+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23866+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23868+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23869+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23872+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23873+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23875+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23877+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23878+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23883+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23885+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23886+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23888+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23889+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.2389+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23892+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23893+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23894+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23896+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23897+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23898+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23901+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23903+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23904+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23905+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23907+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23908+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.2391+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23911+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23913+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23914+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23915+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23916+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23918+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23919+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23921+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23922+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23923+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23925+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23926+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23927+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23929+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.2393+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23931+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23933+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23934+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23935+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23936+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23939+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23945+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23946+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23948+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23949+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.23951+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:30.23952+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:30.24084+08:00 INFO [359133,1c134a3dcf07a68a] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=1c134a3dcf07a68a, body=] 2023-04-29T13:33:30.24097+08:00 INFO [359133,0c55eb5c9fcd161a] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=0c55eb5c9fcd161a, body=] 2023-04-29T13:33:30.24176+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:33:30.24187+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:33:32.72671+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.670011ms 2023-04-29T13:33:32.72677+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:32.82581+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.953714ms 2023-04-29T13:33:32.82588+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:37.7268+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.530808ms 2023-04-29T13:33:37.72686+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:37.8248+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.370206ms 2023-04-29T13:33:37.82486+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:42.7262+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.217804ms 2023-04-29T13:33:42.72626+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:42.82467+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.430607ms 2023-04-29T13:33:42.82474+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:45.23562+08:00 INFO [359133,824cd3ba3951f775] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=824cd3ba3951f775, body=] 2023-04-29T13:33:45.23583+08:00 INFO [359133,523ddeb709a00144] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=523ddeb709a00144, body=] 2023-04-29T13:33:45.23979+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.23985+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.23987+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.23989+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.23991+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.23992+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.23994+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.23997+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.23998+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24002+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24003+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24005+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24006+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24008+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24014+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24016+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24017+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24019+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.2402+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24022+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24024+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24027+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24029+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24031+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24032+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24035+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24037+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.2404+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24041+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24043+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24044+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24046+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24048+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24049+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24051+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24052+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24053+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24056+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24058+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.2406+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24061+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24063+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24064+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24066+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24068+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.2407+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24071+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24073+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24075+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24077+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24078+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.2408+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24081+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24083+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24084+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24086+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24087+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24089+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24091+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24092+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24094+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24095+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24097+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24098+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.241+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24101+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24103+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24104+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24106+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.2411+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24113+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24115+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24116+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24118+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24119+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24121+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24122+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24125+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24127+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24128+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.2413+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24132+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24133+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24135+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24137+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.2414+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24142+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24144+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24145+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24147+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24148+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.2415+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24152+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24154+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24155+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24157+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24159+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.2416+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24162+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24163+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24165+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24344+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24349+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24351+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24354+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24355+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24357+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24359+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.2436+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24362+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24363+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24365+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24367+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24368+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24384+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24387+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.2439+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24392+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24394+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24395+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24397+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:33:45.24399+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:33:45.24554+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:33:45.24558+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:33:45.24614+08:00 INFO [359133,de54c8e8fa14827e] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=de54c8e8fa14827e, body=] 2023-04-29T13:33:47.72681+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.060816ms 2023-04-29T13:33:47.72687+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:47.82567+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.778912ms 2023-04-29T13:33:47.82574+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:52.73796+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.465408ms 2023-04-29T13:33:52.73803+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:52.8253+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.752612ms 2023-04-29T13:33:52.82536+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:57.72669+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.732511ms 2023-04-29T13:33:57.72676+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:33:57.82513+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.544409ms 2023-04-29T13:33:57.82523+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:00.235+08:00 INFO [359133,3245b44b5d373a39] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=3245b44b5d373a39, body=] 2023-04-29T13:34:00.2352+08:00 INFO [359133,07f06310fda318ad] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=07f06310fda318ad, body=] 2023-04-29T13:34:00.23582+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:34:00.2359+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:34:00.23699+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23703+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23711+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23715+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23725+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23728+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23729+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23732+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23737+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23739+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23743+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23747+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23756+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.2376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23762+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23765+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23769+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23777+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23778+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23783+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23815+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23816+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23818+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23819+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.2382+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23823+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23824+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23829+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.2383+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23832+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23833+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23834+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23838+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.2384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23841+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.2391+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23913+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23915+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23916+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23917+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23919+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.2392+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23921+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23923+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23924+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23925+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23927+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23928+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.2393+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23931+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23932+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23934+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23935+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23937+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.2394+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23942+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23943+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23945+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23946+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23948+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23949+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.2395+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23951+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23953+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23954+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.23955+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:00.23957+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:00.24582+08:00 INFO [359133,0010bad32f01e727] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=0010bad32f01e727, body=] 2023-04-29T13:34:02.72668+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.857813ms 2023-04-29T13:34:02.72676+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:02.82618+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.211018ms 2023-04-29T13:34:02.82624+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:07.72666+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.773211ms 2023-04-29T13:34:07.72672+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:07.82522+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.532808ms 2023-04-29T13:34:07.82529+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:12.72699+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.768711ms 2023-04-29T13:34:12.72706+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:12.82467+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.451507ms 2023-04-29T13:34:12.82475+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:15.23582+08:00 INFO [359133,84b0083af7ab5134] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=84b0083af7ab5134, body=] 2023-04-29T13:34:15.23974+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.23982+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.23983+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.23985+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.23987+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.23989+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.2399+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.23992+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.23993+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.23995+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.23997+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.23998+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24001+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24003+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24004+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24006+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24007+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24009+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24011+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24013+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24019+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24021+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24023+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24024+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24026+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24027+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24029+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.2403+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24033+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24034+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24036+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24041+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24043+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24044+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24047+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24049+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.2405+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24052+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24053+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24055+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24057+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24058+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.2406+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24061+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24063+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24065+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24066+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24068+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24069+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24071+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24072+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24075+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24077+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24079+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.2408+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24082+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24084+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24087+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24089+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24091+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24093+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24095+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24096+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24098+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.241+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24101+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24103+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24104+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24106+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24107+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24109+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24111+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24112+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24114+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24119+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24121+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24123+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24124+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24126+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24127+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24129+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24131+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24132+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24134+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24136+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24141+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24143+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24145+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24146+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24148+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24149+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24152+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24153+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24155+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24157+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24158+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24159+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24161+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24162+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24164+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24166+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24342+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24347+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24349+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24351+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24352+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24354+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24356+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24358+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24361+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24364+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24366+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24367+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24369+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24371+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24372+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.2438+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24388+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24389+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24391+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24392+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24394+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24395+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.24397+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24399+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:15.244+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:15.24521+08:00 INFO [359133,ebbb1f07054669ea] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=ebbb1f07054669ea, body=] 2023-04-29T13:34:15.24567+08:00 INFO [359133,127a64939c1a9a4e] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=127a64939c1a9a4e, body=] 2023-04-29T13:34:15.24633+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:34:15.24636+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:34:17.72734+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.30062ms 2023-04-29T13:34:17.72743+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:17.82478+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.572109ms 2023-04-29T13:34:17.82484+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:22.72949+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.383049ms 2023-04-29T13:34:22.72979+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:22.82504+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.238604ms 2023-04-29T13:34:22.82511+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:27.72608+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.528608ms 2023-04-29T13:34:27.72615+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:27.82614+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.179317ms 2023-04-29T13:34:27.8262+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:30.23513+08:00 INFO [359133,4a4e8c77a890e9bc] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=4a4e8c77a890e9bc, body=] 2023-04-29T13:34:30.23605+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23609+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23611+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23613+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23614+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23615+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23617+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23618+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23619+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23621+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23622+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23623+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23625+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23626+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23628+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.2363+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23631+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23632+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23635+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23637+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23639+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23641+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23642+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23643+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23645+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23646+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23647+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23649+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.2365+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23651+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23653+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23654+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23655+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23657+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23658+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23659+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.2366+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23662+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23663+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23664+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23666+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23667+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23668+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.2367+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23671+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23672+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23674+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23675+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23676+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23681+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23683+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23685+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23686+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23687+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23689+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.2369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23691+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23693+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23694+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23697+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23698+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23699+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.237+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23703+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23707+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23711+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23714+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23716+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23717+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23718+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.2372+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23724+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23727+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23738+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23754+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23815+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23817+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23818+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23819+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23829+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.2383+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23834+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23835+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23839+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23841+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23842+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23843+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23846+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23847+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.2385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23851+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23853+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23854+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23855+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23857+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:30.23858+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:30.23984+08:00 INFO [359133,fc852d12f5db8586] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=fc852d12f5db8586, body=] 2023-04-29T13:34:30.2404+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:34:30.24043+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:34:30.24505+08:00 INFO [359133,09f7ee0e35ee75c3] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=09f7ee0e35ee75c3, body=] 2023-04-29T13:34:32.72644+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.64151ms 2023-04-29T13:34:32.72651+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:32.82489+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.545009ms 2023-04-29T13:34:32.82495+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:37.72672+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.834612ms 2023-04-29T13:34:37.72679+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:37.82573+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.275519ms 2023-04-29T13:34:37.82581+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:42.72659+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.410107ms 2023-04-29T13:34:42.72665+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:42.82469+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.494307ms 2023-04-29T13:34:42.82475+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:45.2364+08:00 INFO [359133,9b9d306c5af4e906] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=9b9d306c5af4e906, body=] 2023-04-29T13:34:45.23707+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:34:45.2371+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:34:45.24173+08:00 INFO [359133,1428eaf2ab38fae0] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=1428eaf2ab38fae0, body=] 2023-04-29T13:34:45.24187+08:00 INFO [359133,83da54b7e26cb085] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=83da54b7e26cb085, body=] 2023-04-29T13:34:45.24285+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24289+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24295+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24297+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24298+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.243+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24302+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24303+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24305+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24306+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24307+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24309+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.2431+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24311+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24313+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24314+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24315+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24317+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24318+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24319+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24321+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24322+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24323+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24324+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24326+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24327+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24328+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.2433+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24331+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24332+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24334+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24335+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24336+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24339+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.2434+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24342+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24343+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24344+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24346+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24347+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24349+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.2435+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24351+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24353+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24354+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24355+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24357+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24358+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24359+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.2436+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24362+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24363+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24364+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24365+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24367+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24368+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24369+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24371+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24372+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24374+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24379+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24382+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24383+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24386+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24387+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.2439+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24396+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24397+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24399+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.244+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24401+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24402+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24404+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24405+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24406+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24408+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24409+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24411+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24412+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24413+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24414+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24416+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24417+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24418+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.2442+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24421+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24422+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24424+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24425+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24426+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24429+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.2443+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24431+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24433+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24434+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.2448+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24483+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24485+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24486+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24488+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24489+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24496+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24497+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24499+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.245+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24501+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24503+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24504+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24505+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24507+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24508+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24509+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.2451+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24512+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24513+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24515+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24516+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24518+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24519+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.2452+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24521+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24523+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24524+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24525+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.24527+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:45.24528+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:34:45.2453+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:34:47.72619+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.183203ms 2023-04-29T13:34:47.72628+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:47.82519+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.285005ms 2023-04-29T13:34:47.82525+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:52.73864+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.937315ms 2023-04-29T13:34:52.73872+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:52.82552+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.318719ms 2023-04-29T13:34:52.82559+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:57.72673+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.576009ms 2023-04-29T13:34:57.72679+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:34:57.82495+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.69821ms 2023-04-29T13:34:57.82503+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:00.2369+08:00 INFO [359133,dec39480c367db54] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=dec39480c367db54, body=] 2023-04-29T13:35:00.23722+08:00 INFO [359133,fe97789bd625993c] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=fe97789bd625993c, body=] 2023-04-29T13:35:00.23808+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:35:00.23812+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:35:00.23915+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.23919+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.23922+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.23928+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.23932+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.23935+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.23936+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.2394+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.23942+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.23943+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.23944+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.23946+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.23949+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.2395+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.23952+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.23954+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.23956+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.23957+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.23958+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.23959+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.23961+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.23963+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.23965+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.23966+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.23977+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.23979+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.2398+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.23981+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.23983+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.23984+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.23985+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.23986+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.23989+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.2399+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.23992+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.23993+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.23997+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24001+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24002+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24004+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24005+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24007+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24009+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24011+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24014+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24015+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24025+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24026+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24028+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24029+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.2403+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24032+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24033+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24034+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24035+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24037+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.2404+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24041+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24042+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24044+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24045+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24046+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24048+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24049+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.2405+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24052+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24053+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24055+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24057+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.2406+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24063+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24064+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24066+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24067+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24072+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24074+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24075+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24076+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24078+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24079+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.2408+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24081+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24083+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24084+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24086+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24087+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24088+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.2409+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24091+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24093+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24094+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24095+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24096+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24098+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24099+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.241+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24101+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24103+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24106+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24108+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24109+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24162+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24166+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24172+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24174+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24175+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24176+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24178+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24179+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24181+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24182+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24183+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24186+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24189+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24192+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24194+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24196+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24197+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24198+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.242+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24201+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24202+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24204+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24205+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24207+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24208+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24209+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.2421+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24212+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24213+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24214+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.24216+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:00.24217+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:00.25118+08:00 INFO [359133,7f43338dad2761de] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=7f43338dad2761de, body=] 2023-04-29T13:35:02.72677+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.720511ms 2023-04-29T13:35:02.72684+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:02.82998+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.559881ms 2023-04-29T13:35:02.83004+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:07.72654+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.664211ms 2023-04-29T13:35:07.7266+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:07.82473+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.526008ms 2023-04-29T13:35:07.82479+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:12.72645+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.356906ms 2023-04-29T13:35:12.72651+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:12.82546+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.478808ms 2023-04-29T13:35:12.82552+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:15.23477+08:00 INFO [359133,b398a72764f0fa5c] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=b398a72764f0fa5c, body=] 2023-04-29T13:35:15.23578+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23583+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23584+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23587+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23588+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.2359+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23591+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23592+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23594+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23595+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23598+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23599+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.236+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23602+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23603+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23605+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23606+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23607+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23609+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.2361+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23611+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23613+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23614+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23615+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23617+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23618+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23619+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.2362+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23622+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23623+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23624+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23626+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23627+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23628+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.2363+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23631+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23633+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23634+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23635+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23637+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23639+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23645+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23647+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23648+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23649+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23651+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23652+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23653+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23655+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23656+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23658+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23659+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.2366+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23662+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23663+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23666+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23667+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.2367+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23671+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23673+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23674+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23676+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23677+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23678+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.2368+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23681+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23682+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23684+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23685+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23687+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23688+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23689+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23691+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23692+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23693+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23695+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23696+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23697+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23699+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23701+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23707+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23711+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23715+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23721+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23722+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23801+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23806+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.2381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23812+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23813+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23815+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23816+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.2382+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23821+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23823+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23824+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23825+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23827+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23828+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23829+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23831+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23839+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:15.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:15.23967+08:00 INFO [359133,efc96165e84c4e2a] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=efc96165e84c4e2a, body=] 2023-04-29T13:35:15.23982+08:00 INFO [359133,8d4c5a8aa061e399] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=8d4c5a8aa061e399, body=] 2023-04-29T13:35:15.24056+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:35:15.2406+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:35:17.72663+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.495008ms 2023-04-29T13:35:17.72669+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:17.82559+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.63461ms 2023-04-29T13:35:17.82565+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:22.7262+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.61291ms 2023-04-29T13:35:22.72627+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:22.82441+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.377906ms 2023-04-29T13:35:22.82447+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:27.72628+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.435507ms 2023-04-29T13:35:27.72635+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:27.82513+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.358306ms 2023-04-29T13:35:27.8252+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:30.23512+08:00 INFO [359133,ce96560d3c4e0f06] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=ce96560d3c4e0f06, body=] 2023-04-29T13:35:30.23534+08:00 INFO [359133,08a0d40a0cd79cca] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=08a0d40a0cd79cca, body=] 2023-04-29T13:35:30.23594+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:35:30.23597+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:35:30.23681+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23684+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23686+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23687+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23689+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.2369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23692+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23693+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23694+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23697+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23698+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23701+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.2371+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23712+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23721+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23728+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23729+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23732+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23736+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23739+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23743+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23747+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.2376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23762+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23778+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23783+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23784+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23785+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23793+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.2381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23812+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23813+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23821+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23822+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23824+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23825+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23826+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23828+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23829+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23893+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23898+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23901+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23903+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23904+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23906+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23907+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23908+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.2391+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23911+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23912+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23914+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23915+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23916+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23917+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23919+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.2392+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23921+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23922+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23924+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23925+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23926+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23928+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23929+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.2393+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23932+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23933+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23935+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.23936+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23938+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.2394+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:30.23941+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:30.24549+08:00 INFO [359133,b506f40cc1307188] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=b506f40cc1307188, body=] 2023-04-29T13:35:32.72633+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.758411ms 2023-04-29T13:35:32.72641+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:32.8253+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.458508ms 2023-04-29T13:35:32.82536+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:37.72613+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.289505ms 2023-04-29T13:35:37.72619+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:37.82509+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.442507ms 2023-04-29T13:35:37.82515+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:42.72883+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.70284ms 2023-04-29T13:35:42.7289+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:42.82486+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.308705ms 2023-04-29T13:35:42.82497+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:45.23536+08:00 INFO [359133,9a7878f5206a336d] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=9a7878f5206a336d, body=] 2023-04-29T13:35:45.24039+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24045+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24048+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.2405+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24051+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24053+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24056+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24057+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24059+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.2406+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24062+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24063+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24065+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24067+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24068+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.2407+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24071+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24073+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24074+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24076+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24077+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24079+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24081+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24082+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24084+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24086+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24088+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24089+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24091+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24093+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24095+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24101+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24103+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24104+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24106+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24107+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24109+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24111+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24113+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24114+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24116+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24117+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24119+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.2412+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24122+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24124+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24125+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24127+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24128+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.2413+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24131+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24133+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24134+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24136+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.2414+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24141+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24143+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24145+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24147+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24148+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.2415+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24153+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24154+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24156+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24157+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24159+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.2416+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24162+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24163+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24165+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24166+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24168+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24169+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24171+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24172+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24174+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24175+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24177+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24178+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.2418+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24182+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24184+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24185+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24187+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24188+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.2419+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24191+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24193+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24195+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.242+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24202+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24204+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24205+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24207+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24209+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.2421+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24212+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24214+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24215+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24217+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24218+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.2422+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24388+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24392+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24394+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24395+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24404+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24407+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24409+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.2441+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24412+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24415+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24417+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24418+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.2442+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24422+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24424+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24425+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24427+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24428+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.2443+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24431+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24433+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24434+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24436+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24439+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24441+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24443+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24445+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24446+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24448+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24449+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.24451+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:35:45.24453+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:35:45.2451+08:00 INFO [359133,f3edf2cf1643465d] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=f3edf2cf1643465d, body=] 2023-04-29T13:35:45.24551+08:00 INFO [359133,3dea66d6bbc92880] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=3dea66d6bbc92880, body=] 2023-04-29T13:35:45.24614+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:35:45.24617+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:35:47.73092+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.192132ms 2023-04-29T13:35:47.73099+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:47.82488+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.293005ms 2023-04-29T13:35:47.82495+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:52.73752+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.515008ms 2023-04-29T13:35:52.73759+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:52.84626+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.750212ms 2023-04-29T13:35:52.84633+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:57.72648+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.134203ms 2023-04-29T13:35:57.72655+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:35:57.82476+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.789011ms 2023-04-29T13:35:57.82482+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:00.23494+08:00 INFO [359133,6de66de643976951] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=6de66de643976951, body=] 2023-04-29T13:36:00.2359+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23594+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23597+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.236+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23602+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23603+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23605+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23606+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23607+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23608+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.2361+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23611+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23613+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23614+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23616+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23617+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23618+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.2362+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23621+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23622+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23624+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23625+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23626+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23628+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.2363+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23631+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23633+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23634+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23635+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23636+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23639+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23641+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23642+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23643+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23645+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23646+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23648+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23649+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.2365+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23652+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23653+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23654+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23656+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23657+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23658+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.2366+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23661+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23662+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23664+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23665+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23666+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.2367+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23671+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23673+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23674+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23675+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23678+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.2368+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23681+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23683+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23684+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23686+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23688+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23689+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.2369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23692+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23694+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23696+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23697+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23698+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.237+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23703+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23711+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23713+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23714+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23716+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23717+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23719+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23721+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23722+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23723+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23727+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.2373+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23733+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23737+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23739+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23745+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23746+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23749+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23804+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23806+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23807+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23816+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23818+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23829+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23832+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23833+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23839+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23841+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23845+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23846+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23849+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.2385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:00.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:00.23964+08:00 INFO [359133,f314d353efbde4cc] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=f314d353efbde4cc, body=] 2023-04-29T13:36:00.23977+08:00 INFO [359133,3376d2507d5aff25] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=3376d2507d5aff25, body=] 2023-04-29T13:36:00.24051+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:36:00.24055+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:36:02.72709+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.025115ms 2023-04-29T13:36:02.72716+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:02.82508+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.377706ms 2023-04-29T13:36:02.82514+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:07.72626+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.410707ms 2023-04-29T13:36:07.72633+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:07.82461+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.206204ms 2023-04-29T13:36:07.82469+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:12.72801+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.687825ms 2023-04-29T13:36:12.72807+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:12.82534+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.728111ms 2023-04-29T13:36:12.82543+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:15.2354+08:00 INFO [359133,86f09f3276c0b241] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=86f09f3276c0b241, body=] 2023-04-29T13:36:15.23567+08:00 INFO [359133,8e7f58ba530bff94] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=8e7f58ba530bff94, body=] 2023-04-29T13:36:15.23635+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:36:15.23646+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:36:15.23756+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23761+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23777+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23778+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23786+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23787+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23788+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.2379+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23791+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23793+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23806+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23812+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23813+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23815+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23816+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23819+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.2382+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23821+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23823+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23824+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23825+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23827+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23828+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.2383+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23831+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23834+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23835+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23839+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.2384+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23842+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23843+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23844+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23846+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23847+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23848+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.2385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23851+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23852+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23861+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23862+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23864+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23865+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23867+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23868+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23869+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23872+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23873+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23875+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23876+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23877+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23878+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.2388+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23881+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23882+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23884+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23887+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23888+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.2389+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23891+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23892+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23894+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23895+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23897+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23898+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23899+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.239+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23902+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23903+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23905+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23906+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23908+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.2391+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23911+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23965+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23969+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.2397+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23972+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23974+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23975+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23977+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23978+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23979+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23981+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23982+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23983+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23985+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23986+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23988+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23989+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23991+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23992+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23993+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23995+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23996+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.23997+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.23999+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.24+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.24001+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.24003+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.24004+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.24005+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.24007+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.24008+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.24009+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:15.2401+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:15.24536+08:00 INFO [359133,e4237b07250599d0] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=e4237b07250599d0, body=] 2023-04-29T13:36:17.72626+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.106202ms 2023-04-29T13:36:17.72632+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:17.82519+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.564509ms 2023-04-29T13:36:17.82525+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:22.72686+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.703311ms 2023-04-29T13:36:22.72692+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:22.82549+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.61331ms 2023-04-29T13:36:22.82556+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:27.72679+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.530208ms 2023-04-29T13:36:27.72685+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:27.82486+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.359406ms 2023-04-29T13:36:27.82493+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:30.23489+08:00 INFO [359133,61b9973fbad5b67b] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=61b9973fbad5b67b, body=] 2023-04-29T13:36:30.23584+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23589+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23591+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23592+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23594+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23595+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.236+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23602+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23604+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23605+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23606+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23608+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23609+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.2361+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23612+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23613+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23615+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23617+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23618+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23619+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23621+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23622+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23623+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23625+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23626+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23627+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23629+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.2363+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23631+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23633+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23634+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23635+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23636+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23641+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23644+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23647+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23649+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.2365+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23652+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23654+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23655+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23656+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23658+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23659+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23661+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23662+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23663+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23664+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23666+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23669+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.2367+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23672+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23673+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23674+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23676+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23677+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23678+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.2368+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23681+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23682+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23683+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23685+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23686+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23687+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.2369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23691+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23693+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23694+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23725+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23728+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23729+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23732+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23739+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23759+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.2376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23762+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23827+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23829+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.2383+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23832+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23833+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.2384+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23841+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23843+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23844+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23845+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23847+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.2385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23851+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23853+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23854+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23855+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23857+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23858+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23859+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23862+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23864+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23865+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23866+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.23868+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23869+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.2387+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:30.23872+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:30.24007+08:00 INFO [359133,db793c40ceb8b1c0] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=db793c40ceb8b1c0, body=] 2023-04-29T13:36:30.24019+08:00 INFO [359133,a7d4b519d5deffe6] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=a7d4b519d5deffe6, body=] 2023-04-29T13:36:30.241+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:36:30.24104+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:36:32.72968+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.718854ms 2023-04-29T13:36:32.72975+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:32.82703+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.76524ms 2023-04-29T13:36:32.82709+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:37.72693+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.944214ms 2023-04-29T13:36:37.727+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:37.82483+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.413106ms 2023-04-29T13:36:37.82489+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:42.72577+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.802998ms 2023-04-29T13:36:42.72588+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:42.82499+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.376406ms 2023-04-29T13:36:42.82506+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:45.23494+08:00 INFO [359133,e3d36b9e82469ce5] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=e3d36b9e82469ce5, body=] 2023-04-29T13:36:45.23602+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23607+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23608+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.2361+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23611+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23613+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23614+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23615+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23617+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23618+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.2362+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23622+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23624+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23625+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23626+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23628+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23629+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.2363+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23632+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23633+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23635+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23636+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23638+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.2364+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23641+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23642+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23644+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23645+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23646+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23648+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23649+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.2365+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23652+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23653+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23654+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23656+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23657+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23658+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.2366+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23661+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23662+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23664+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23665+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23666+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23668+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23669+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23671+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23672+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23673+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23674+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23676+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23677+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23678+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.2368+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23681+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23686+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23688+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23689+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.2369+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23692+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23693+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23694+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23695+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23697+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23698+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23699+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23701+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23702+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23704+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23705+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23706+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23708+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23709+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.2371+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23712+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23713+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23714+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23716+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23717+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23719+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.2372+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23723+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23724+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23725+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23727+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23728+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23729+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23732+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23733+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23736+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23739+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23747+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.238+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23816+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23818+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23819+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.2382+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23823+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23824+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23825+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23827+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23828+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23829+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23835+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23839+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.2384+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23841+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23843+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23844+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23845+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:36:45.23847+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:36:45.23956+08:00 INFO [359133,c18c18e758579d5d] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=c18c18e758579d5d, body=] 2023-04-29T13:36:45.23968+08:00 INFO [359133,08682a0ba1132405] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=08682a0ba1132405, body=] 2023-04-29T13:36:45.24042+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:36:45.24046+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:36:47.72599+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.280204ms 2023-04-29T13:36:47.72606+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:47.82501+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.234804ms 2023-04-29T13:36:47.82507+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:52.7386+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.709011ms 2023-04-29T13:36:52.73872+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:52.82533+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.171417ms 2023-04-29T13:36:52.82541+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:57.72598+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.047301ms 2023-04-29T13:36:57.72605+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:36:57.82498+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.352806ms 2023-04-29T13:36:57.82503+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:00.23511+08:00 INFO [359133,35a9836cc15b50bb] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=35a9836cc15b50bb, body=] 2023-04-29T13:37:00.23528+08:00 INFO [359133,5e77428428f6f24b] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=5e77428428f6f24b, body=] 2023-04-29T13:37:00.23591+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:37:00.23595+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:37:00.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23713+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23715+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23721+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23727+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23739+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23741+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23745+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23747+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23761+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23762+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23768+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23769+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23772+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23788+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.2379+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23793+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23794+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23798+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23802+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23806+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23807+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.2381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23811+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23813+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23822+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23824+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23825+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23827+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23828+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23829+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23831+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23834+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23839+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23841+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23844+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23846+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23849+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23851+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23856+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23861+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23864+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23866+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23869+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23877+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.2388+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23882+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23884+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23887+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23889+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23892+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23894+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23956+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.2396+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23962+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23964+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23965+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23967+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23968+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23969+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23974+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23977+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23987+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23988+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23989+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23991+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23992+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23994+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23995+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23996+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.23997+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.23999+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.24+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.24001+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.24003+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.24004+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.24005+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.24007+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.24008+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.24009+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.24011+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.24012+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.24013+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:00.24015+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:00.24566+08:00 INFO [359133,4eda7156338131a9] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=4eda7156338131a9, body=] 2023-04-29T13:37:02.7268+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.781612ms 2023-04-29T13:37:02.72687+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:02.82586+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.422521ms 2023-04-29T13:37:02.82593+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:07.72629+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.468607ms 2023-04-29T13:37:07.72636+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:07.82506+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.216203ms 2023-04-29T13:37:07.82512+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:12.72648+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.771012ms 2023-04-29T13:37:12.72654+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:12.82473+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.515408ms 2023-04-29T13:37:12.82479+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:15.23492+08:00 INFO [359133,1e3d9566c5c0c4e8] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=1e3d9566c5c0c4e8, body=] 2023-04-29T13:37:15.23513+08:00 INFO [359133,38870153c2685821] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=38870153c2685821, body=] 2023-04-29T13:37:15.23603+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23608+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23609+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23611+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23612+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23613+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23615+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23616+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23617+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23619+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.2362+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23621+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23623+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23624+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23626+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23627+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23628+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.2363+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23631+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23632+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23634+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23635+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23636+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23639+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.2364+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23642+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23643+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23644+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23646+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23647+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23649+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.2365+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23651+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23652+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23654+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23655+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23657+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23658+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.2366+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23661+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23662+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23663+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23665+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23666+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23667+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23673+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23674+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23675+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23677+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23678+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.2368+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23681+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23682+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23683+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23685+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23686+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23688+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23689+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.2369+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23692+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23693+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23694+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23696+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23697+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23699+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.237+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23706+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23707+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23709+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.2371+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23711+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23713+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23714+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23715+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23717+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23718+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23725+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23727+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.2373+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23734+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23739+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23746+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23749+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.2375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23816+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23822+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23829+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23832+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23833+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23838+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.2384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23841+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:15.2385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:15.23923+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:37:15.23927+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:37:15.24474+08:00 INFO [359133,893997080b4035c9] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=893997080b4035c9, body=] 2023-04-29T13:37:17.72606+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.192203ms 2023-04-29T13:37:17.72615+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:17.82521+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.508708ms 2023-04-29T13:37:17.82527+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:22.72544+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.018101ms 2023-04-29T13:37:22.72551+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:22.82555+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.994515ms 2023-04-29T13:37:22.82562+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:27.72646+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.055402ms 2023-04-29T13:37:27.72652+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:27.82459+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.460507ms 2023-04-29T13:37:27.82466+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:30.23515+08:00 INFO [359133,14495800b404f802] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=14495800b404f802, body=] 2023-04-29T13:37:30.23605+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23611+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23613+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23614+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23616+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23617+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23618+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23621+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23624+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23625+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23627+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23628+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23629+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23631+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23632+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23633+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23635+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23636+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23639+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.2364+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23641+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23643+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23644+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23645+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23647+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23648+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23649+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23651+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23652+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23654+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23655+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23656+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23658+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.2366+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23661+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23662+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23663+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23665+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23666+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23667+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23668+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.2367+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23671+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23672+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23673+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23675+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23676+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23677+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23678+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.2368+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23681+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23682+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23683+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23685+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23686+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23687+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23689+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.2369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23691+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23693+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23694+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23696+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23698+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23699+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23701+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23703+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23707+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23711+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23715+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23716+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23718+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23719+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.2372+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23723+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23724+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23725+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23727+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23728+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23729+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23732+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23733+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23736+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23738+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.2374+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23741+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23744+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23745+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23746+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23748+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23749+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23799+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23802+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23803+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23806+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23807+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.2381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23811+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23813+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23822+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23826+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23832+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23833+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.23836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23839+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:30.2384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:30.23997+08:00 INFO [359133,ae61de302d9c7bfe] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=ae61de302d9c7bfe, body=] 2023-04-29T13:37:30.24011+08:00 INFO [359133,a6619e57754759cd] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=a6619e57754759cd, body=] 2023-04-29T13:37:30.24085+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:37:30.24088+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:37:32.72633+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.9773ms 2023-04-29T13:37:32.72641+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:32.8244+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.450907ms 2023-04-29T13:37:32.82446+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:37.72688+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.61331ms 2023-04-29T13:37:37.72699+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:37.82542+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.485508ms 2023-04-29T13:37:37.82552+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:42.72628+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.208903ms 2023-04-29T13:37:42.72635+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:42.82518+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.200404ms 2023-04-29T13:37:42.82525+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:45.23501+08:00 INFO [359133,bcc311a4d7208869] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=bcc311a4d7208869, body=] 2023-04-29T13:37:45.23597+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23601+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23603+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23604+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23606+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23607+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23608+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.2361+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23611+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23613+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23614+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23615+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23616+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23618+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23619+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23621+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23622+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23623+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23625+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23626+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23627+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23628+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.2363+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23631+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23632+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23634+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23635+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23636+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.2364+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23641+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23642+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23643+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23645+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23646+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23647+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23649+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23653+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23655+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23656+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23658+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23659+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23661+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23662+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23663+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23665+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23666+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23667+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.2367+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23671+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23672+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23674+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23675+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23676+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23678+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23679+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.2368+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23682+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23683+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23684+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23685+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23687+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23688+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.2369+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23692+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23693+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23696+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23697+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23699+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.237+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23701+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23703+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23704+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23705+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23707+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23708+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23709+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23711+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23712+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23713+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23714+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23716+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23717+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23718+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.2372+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23725+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23727+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.2373+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23734+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23738+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.2374+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23741+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23744+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23798+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23802+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23812+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23813+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23816+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.2382+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23821+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23822+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23824+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23825+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23826+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23828+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23829+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23834+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23835+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:37:45.23839+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:37:45.23947+08:00 INFO [359133,b05c1eca0dc9f3d5] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=b05c1eca0dc9f3d5, body=] 2023-04-29T13:37:45.23967+08:00 INFO [359133,94f21cfbbb3dd69d] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=94f21cfbbb3dd69d, body=] 2023-04-29T13:37:45.24036+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:37:45.24041+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:37:47.72688+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.465507ms 2023-04-29T13:37:47.72694+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:47.82461+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.044702ms 2023-04-29T13:37:47.82467+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:52.75496+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=24.916758ms 2023-04-29T13:37:52.75502+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:52.82459+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.445907ms 2023-04-29T13:37:52.82466+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:57.72594+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.401606ms 2023-04-29T13:37:57.72604+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:37:57.82481+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.809912ms 2023-04-29T13:37:57.82487+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:00.23724+08:00 INFO [359133,d9d13847bb89a9a7] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=d9d13847bb89a9a7, body=] 2023-04-29T13:38:00.23747+08:00 INFO [359133,7d4963e8dbf96db0] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=7d4963e8dbf96db0, body=] 2023-04-29T13:38:00.23817+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:38:00.23821+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:38:00.23923+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.23928+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.23929+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.23931+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.23932+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.23934+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.23935+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.23936+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.23942+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.23943+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.23945+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.23946+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.23948+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.23953+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.23955+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.23956+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.23958+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.23959+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.2396+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.23962+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.23964+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.23966+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.23967+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.23968+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.2397+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.23971+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.23972+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.23973+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.23975+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.23976+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.23977+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.23979+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.2398+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.23981+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.23982+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.23984+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.23985+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.23986+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.23988+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.23989+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.2399+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.23992+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.23993+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.23994+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.23996+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.23998+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24002+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24004+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24006+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24007+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24008+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.2401+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24011+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24013+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24014+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24016+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24017+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24018+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.2402+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24021+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24022+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24024+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24025+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24026+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24028+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24029+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24031+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24032+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24034+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24035+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24036+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24039+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.2404+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24042+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24043+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24045+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24046+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24047+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24058+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.2406+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24062+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24063+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24065+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24066+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24067+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24069+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.2407+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24072+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24073+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24075+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24076+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.2408+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24082+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24083+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24085+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24086+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24087+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24088+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.2409+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24092+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24093+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24094+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24155+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24162+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24164+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24165+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24167+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24168+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.2417+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24171+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24172+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24174+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24175+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24176+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24178+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24179+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.2418+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24182+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24183+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24184+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24189+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24191+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24194+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24195+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24197+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24198+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24199+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24201+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24202+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24203+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24204+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24206+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24207+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:00.24208+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:00.24789+08:00 INFO [359133,0acdf4e7a79b9ba7] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=0acdf4e7a79b9ba7, body=] 2023-04-29T13:38:02.73257+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.283091ms 2023-04-29T13:38:02.73264+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:02.82522+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.342206ms 2023-04-29T13:38:02.82528+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:07.72652+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.717711ms 2023-04-29T13:38:07.72662+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:07.83147+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.278006ms 2023-04-29T13:38:07.83155+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:12.72751+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.212218ms 2023-04-29T13:38:12.72758+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:12.82427+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.344605ms 2023-04-29T13:38:12.82433+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:15.23574+08:00 INFO [359133,f71f2e77e57958e3] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=f71f2e77e57958e3, body=] 2023-04-29T13:38:15.23595+08:00 INFO [359133,762bc8f319a30c03] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=762bc8f319a30c03, body=] 2023-04-29T13:38:15.2367+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:38:15.23674+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:38:15.24325+08:00 INFO [359133,e00eb28fb363f421] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=e00eb28fb363f421, body=] 2023-04-29T13:38:15.24673+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24678+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.2468+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24682+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24683+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24685+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24686+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24688+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.2469+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24691+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24693+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24694+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24696+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24697+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.247+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24701+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24705+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24706+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24708+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.2471+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24711+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.2472+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24725+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24727+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24728+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.2473+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24739+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24741+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24762+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24765+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.2477+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24772+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24774+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24775+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24777+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.2478+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24783+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24786+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24788+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24791+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24793+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24794+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.248+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24811+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24813+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24816+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24819+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.2482+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.2483+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24849+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24857+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24859+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.2486+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24862+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24863+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24865+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24866+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24868+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24869+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.24871+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.24872+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.25175+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.25179+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.25181+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.25183+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.25184+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.25186+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.25187+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.25188+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.2519+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.25191+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.25192+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.25194+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.25195+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.25197+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.25198+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.252+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.25201+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.25202+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.25204+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.25205+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.25206+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.25208+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.25209+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.2521+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.25212+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.25213+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.25214+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.25215+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.25217+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.25218+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:15.25219+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:15.25221+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:17.72589+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.474207ms 2023-04-29T13:38:17.72595+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:17.82521+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.771811ms 2023-04-29T13:38:17.82527+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:22.72628+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.578609ms 2023-04-29T13:38:22.72636+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:22.82491+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.534408ms 2023-04-29T13:38:22.82498+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:27.72616+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.558408ms 2023-04-29T13:38:27.72622+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:27.82512+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.286505ms 2023-04-29T13:38:27.82518+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:30.23502+08:00 INFO [359133,7b47b981dad5092b] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=7b47b981dad5092b, body=] 2023-04-29T13:38:30.23631+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23641+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23644+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23645+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23647+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23648+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23649+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23658+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.2366+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23661+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23662+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23664+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23665+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23666+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23668+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23669+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23671+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23682+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23684+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23693+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23695+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23696+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23697+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23698+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23701+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23707+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23711+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23715+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23721+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23722+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23739+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23746+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23748+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23752+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23753+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23756+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.2376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23762+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23793+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23796+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23797+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23799+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.238+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23802+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23803+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23804+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23806+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23807+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.2381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23811+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23822+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23874+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23881+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23883+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23884+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23886+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23887+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23888+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.2389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23891+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23892+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23894+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23895+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23896+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23898+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23899+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23901+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23902+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23904+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23905+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23906+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23908+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23909+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.2391+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23911+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23913+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23914+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23915+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23917+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.23918+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23919+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.2392+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:30.23922+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:30.24067+08:00 INFO [359133,72932ee5395a9f1a] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=72932ee5395a9f1a, body=] 2023-04-29T13:38:30.24094+08:00 INFO [359133,84aaaac7b3608a0f] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=84aaaac7b3608a0f, body=] 2023-04-29T13:38:30.24217+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:38:30.24221+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:38:32.72682+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.503907ms 2023-04-29T13:38:32.72689+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:32.8248+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.318805ms 2023-04-29T13:38:32.82487+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:37.72685+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.821112ms 2023-04-29T13:38:37.72692+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:37.82439+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.460407ms 2023-04-29T13:38:37.82445+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:42.72603+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.768698ms 2023-04-29T13:38:42.7261+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:42.8255+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.830712ms 2023-04-29T13:38:42.82557+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:45.23532+08:00 INFO [359133,e446bb61a8fb4a46] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=e446bb61a8fb4a46, body=] 2023-04-29T13:38:45.23551+08:00 INFO [359133,d1a5fc93077f56a9] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=d1a5fc93077f56a9, body=] 2023-04-29T13:38:45.23998+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:38:45.24005+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:38:45.24288+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24293+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24295+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24297+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24299+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24301+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24302+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24304+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24306+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24308+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24309+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24311+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24312+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24314+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24316+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24318+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24319+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24322+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24323+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24325+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24326+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24328+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24329+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24331+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24332+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24334+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24335+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24338+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.2434+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24342+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24343+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24345+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24356+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24358+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24359+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24361+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24362+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24364+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24365+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24367+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24368+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.2437+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24379+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24389+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.2439+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24392+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24393+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24395+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24396+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24398+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24401+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24402+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24404+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24406+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24407+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24409+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24411+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24413+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24425+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24427+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24428+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.2443+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24431+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24433+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24434+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24436+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24438+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24441+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24442+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24444+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24445+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24447+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24449+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.2445+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24452+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24453+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24455+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24456+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24458+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.2446+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24462+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24464+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24465+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24467+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24469+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24471+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24475+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24478+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.2448+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24481+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24483+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24484+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24509+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24511+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24513+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24651+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24655+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24657+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24659+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.2466+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24663+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24665+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24683+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24684+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24687+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24698+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.247+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24701+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24703+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24704+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24723+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24727+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24733+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24734+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24736+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24739+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.24744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:38:45.24745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:38:45.25649+08:00 INFO [359133,bb01a030ef09f674] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=bb01a030ef09f674, body=] 2023-04-29T13:38:47.72621+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.450508ms 2023-04-29T13:38:47.7263+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:47.82545+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.526408ms 2023-04-29T13:38:47.82552+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:52.74956+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=14.226605ms 2023-04-29T13:38:52.74963+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:52.82553+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.172617ms 2023-04-29T13:38:52.82561+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:57.72647+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.417207ms 2023-04-29T13:38:57.72654+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:38:57.8244+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.166703ms 2023-04-29T13:38:57.82447+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:00.23494+08:00 INFO [359133,8d25f9892dd07869] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=8d25f9892dd07869, body=] 2023-04-29T13:39:00.23588+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23592+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23594+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23595+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23597+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23598+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.236+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23602+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23603+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23604+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23606+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23607+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23609+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.2361+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23613+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23614+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23616+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23617+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23618+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23619+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23621+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23622+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23623+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23625+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23626+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23627+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23629+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.2363+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23631+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23633+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23634+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23636+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23638+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.2364+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23643+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23645+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23647+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23648+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23651+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23652+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23653+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23655+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23657+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23658+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23659+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23661+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23662+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23663+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23665+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23666+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23667+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23672+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23673+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23675+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23676+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23677+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23679+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.2368+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23681+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23682+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23684+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23685+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23687+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23688+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.2369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23691+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23692+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23694+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23696+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23698+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23699+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.237+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23703+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23704+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23707+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23708+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23718+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23719+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23721+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23722+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23727+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23738+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23787+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23793+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23797+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23799+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.238+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23801+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23803+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23804+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.2381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23811+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23813+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23821+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23822+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23826+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23829+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:00.23831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:00.23952+08:00 INFO [359133,42b0f77a2253644c] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=42b0f77a2253644c, body=] 2023-04-29T13:39:00.23968+08:00 INFO [359133,86ec6c3514964cc5] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=86ec6c3514964cc5, body=] 2023-04-29T13:39:00.2405+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:39:00.24054+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:39:02.73079+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.375377ms 2023-04-29T13:39:02.73086+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:02.8252+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.863613ms 2023-04-29T13:39:02.82526+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:07.72618+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.333305ms 2023-04-29T13:39:07.72624+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:07.8255+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.913714ms 2023-04-29T13:39:07.82558+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:12.72651+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.894814ms 2023-04-29T13:39:12.72658+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:12.82663+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.701839ms 2023-04-29T13:39:12.82669+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:15.23499+08:00 INFO [359133,f205fdfab741432d] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=f205fdfab741432d, body=] 2023-04-29T13:39:15.23587+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23591+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23593+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23595+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23597+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23598+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.236+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23601+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23602+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23604+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23605+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23606+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23607+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23609+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.2361+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23612+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23613+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23614+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23616+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23618+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.2362+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23621+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23622+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23624+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23625+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23626+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23628+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23629+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.2363+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23632+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23634+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23636+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23638+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.2364+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23641+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23642+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23644+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23645+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23647+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23648+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23649+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23651+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23652+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23653+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23656+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23659+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23661+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23662+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23663+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23665+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23666+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23667+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23669+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.2367+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23671+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23673+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23674+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23675+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23676+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23678+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23679+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.2368+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23682+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23683+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23684+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23685+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23687+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23688+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23689+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23691+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23693+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23694+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23696+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23697+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23698+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23699+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23701+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23702+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23705+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23706+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23707+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.2371+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23711+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23715+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23721+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23722+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23783+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23785+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23792+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23794+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23815+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23817+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23818+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23829+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:15.2383+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:15.23951+08:00 INFO [359133,0d7f5d17aa44b0d9] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=0d7f5d17aa44b0d9, body=] 2023-04-29T13:39:15.23965+08:00 INFO [359133,9c779600476c52eb] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=9c779600476c52eb, body=] 2023-04-29T13:39:15.24031+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:39:15.24034+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:39:17.72612+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.515008ms 2023-04-29T13:39:17.7262+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:17.82518+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.63521ms 2023-04-29T13:39:17.82525+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:22.72682+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.519808ms 2023-04-29T13:39:22.72702+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:22.82514+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.286105ms 2023-04-29T13:39:22.82521+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:27.72609+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.140003ms 2023-04-29T13:39:27.72616+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:27.82491+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.301605ms 2023-04-29T13:39:27.82497+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:30.23653+08:00 INFO [359133,c45c98f151cd61e0] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=c45c98f151cd61e0, body=] 2023-04-29T13:39:30.23761+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23768+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23769+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23772+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23777+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23781+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23783+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23784+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23785+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23786+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23789+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.2379+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23793+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23794+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23798+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23799+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23802+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23803+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23806+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23807+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.2381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23811+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23813+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23815+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23816+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23818+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23828+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23829+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23834+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23837+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.2384+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23841+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23844+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23845+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23846+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23848+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23849+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.2385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23853+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23861+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23862+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23864+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23865+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23866+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23868+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23869+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23872+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23879+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23881+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23882+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23884+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23885+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23886+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23887+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23889+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.2389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23892+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23893+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23894+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23896+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23897+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23898+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.239+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23901+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23903+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23904+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23905+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23907+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23908+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23909+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23911+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23912+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23914+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23915+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23968+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23971+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23977+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23979+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.2398+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23982+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23983+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23984+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23986+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23987+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23988+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.2399+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23991+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23992+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23994+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23995+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23996+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.23997+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.23999+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.24+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.24001+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.24003+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.24004+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.24005+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.24007+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.24008+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.24009+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.24011+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.24012+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.24013+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.24014+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:30.24016+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:30.24149+08:00 INFO [359133,ba28dfbe851d8058] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=ba28dfbe851d8058, body=] 2023-04-29T13:39:30.24162+08:00 INFO [359133,72cd62a98b2b6b86] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=72cd62a98b2b6b86, body=] 2023-04-29T13:39:30.24245+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:39:30.24248+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:39:32.72746+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.246818ms 2023-04-29T13:39:32.72752+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:32.82446+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.284705ms 2023-04-29T13:39:32.82452+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:37.72609+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.65921ms 2023-04-29T13:39:37.72616+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:37.82606+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.248119ms 2023-04-29T13:39:37.82612+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:42.72696+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.991215ms 2023-04-29T13:39:42.72703+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:42.82517+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.447307ms 2023-04-29T13:39:42.82523+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:45.23494+08:00 INFO [359133,794d4ebf8ca21083] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=794d4ebf8ca21083, body=] 2023-04-29T13:39:45.2351+08:00 INFO [359133,bf5f267a40825caf] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=bf5f267a40825caf, body=] 2023-04-29T13:39:45.23574+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:39:45.23578+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:39:45.23669+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23673+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23675+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23676+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23678+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23679+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.2368+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23681+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23683+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23684+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23687+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23688+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23689+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23691+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23692+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23693+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23695+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23696+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23697+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23699+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23701+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23706+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23708+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23709+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.2371+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23712+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23713+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23714+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23715+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23717+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23727+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23737+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.2376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23761+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23765+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23768+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23769+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23778+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23781+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23783+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23784+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23785+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23789+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23794+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23816+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23817+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23822+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23824+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23871+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23875+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23878+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23879+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23881+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23882+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23883+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23885+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23886+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23887+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23888+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.2389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23891+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23892+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23894+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23895+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23896+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23897+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23899+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23901+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23902+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23904+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23906+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23907+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23908+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23909+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23911+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23912+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23914+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.23915+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:39:45.23916+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:39:45.24546+08:00 INFO [359133,f97cbe411e13cd61] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=f97cbe411e13cd61, body=] 2023-04-29T13:39:47.72588+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.101602ms 2023-04-29T13:39:47.72594+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:47.8249+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.115802ms 2023-04-29T13:39:47.82496+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:52.76174+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=34.222091ms 2023-04-29T13:39:52.7618+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:52.82519+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.029315ms 2023-04-29T13:39:52.82525+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:57.72558+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.810498ms 2023-04-29T13:39:57.72566+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:39:57.82457+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.843799ms 2023-04-29T13:39:57.82463+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:00.23485+08:00 INFO [359133,99e16e3e3935ee5e] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=99e16e3e3935ee5e, body=] 2023-04-29T13:40:00.23502+08:00 INFO [359133,ced6ab38714d7ea3] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=ced6ab38714d7ea3, body=] 2023-04-29T13:40:00.23569+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:40:00.23574+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:40:00.23674+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23679+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.2368+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23682+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23683+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23685+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23687+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23689+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23692+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23694+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23696+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23697+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23699+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.237+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23703+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23704+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23707+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23708+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23711+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23715+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23721+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23722+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23728+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23732+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23736+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23739+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23749+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23754+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23756+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23761+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23765+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23769+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23773+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23777+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23781+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23783+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23787+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23788+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23791+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23792+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23793+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23795+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23812+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23815+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23816+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23818+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23819+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23823+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23827+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23829+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.2383+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23832+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23834+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23852+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23854+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23855+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23859+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23862+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23864+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23866+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23868+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23869+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23871+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23872+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23874+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23875+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23877+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23878+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.2388+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23881+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23882+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23885+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23886+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23887+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23889+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.2389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23891+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23893+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23894+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23895+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23897+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.23898+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.23899+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:00.239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:00.24722+08:00 INFO [359133,30b5355a8c933ce6] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=30b5355a8c933ce6, body=] 2023-04-29T13:40:02.72542+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.014001ms 2023-04-29T13:40:02.72548+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:02.82503+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.368006ms 2023-04-29T13:40:02.82511+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:07.72623+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.558708ms 2023-04-29T13:40:07.7263+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:07.82491+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.498007ms 2023-04-29T13:40:07.82497+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:12.72585+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.174203ms 2023-04-29T13:40:12.72592+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:12.82453+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.335305ms 2023-04-29T13:40:12.82459+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:15.23488+08:00 INFO [359133,d3dffc07f8a5cfb2] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=d3dffc07f8a5cfb2, body=] 2023-04-29T13:40:15.23509+08:00 INFO [359133,5b8516e86bc44cb6] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=5b8516e86bc44cb6, body=] 2023-04-29T13:40:15.23832+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23846+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23848+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.2385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23865+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23875+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23877+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23879+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23881+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23882+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23884+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23885+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23887+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23889+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.2389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23895+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23897+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23899+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23901+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23903+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23904+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23906+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23907+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23909+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.2391+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23912+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23914+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23915+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23941+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23943+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23944+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23946+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23948+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23949+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23951+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23952+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23959+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23961+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23962+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23964+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23965+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23967+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23969+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.2397+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23972+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23973+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23975+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23977+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23978+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.2398+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23982+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23984+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23986+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.23987+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.23988+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.2399+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24006+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24008+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.2401+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24011+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24013+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24014+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24016+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24017+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24019+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24021+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24022+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24024+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24025+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24027+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24029+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.2403+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24032+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24033+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24035+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24036+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24039+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24041+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24043+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24045+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24046+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24048+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24049+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24051+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24069+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24072+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24073+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24075+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24076+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24078+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24079+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24081+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24082+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24084+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24086+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24087+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.2409+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24092+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24093+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24095+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24096+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24313+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24317+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24321+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24323+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24334+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24343+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24345+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24347+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24349+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24351+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24352+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24359+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24361+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24362+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24364+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24366+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24367+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24374+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.2438+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.2439+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:15.24391+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:15.24587+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:40:15.24592+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:40:15.25319+08:00 INFO [359133,975d21e268eca910] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=975d21e268eca910, body=] 2023-04-29T13:40:17.72682+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.787212ms 2023-04-29T13:40:17.72688+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:17.82484+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.497908ms 2023-04-29T13:40:17.8249+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:22.72793+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.212033ms 2023-04-29T13:40:22.72801+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:22.82549+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.872113ms 2023-04-29T13:40:22.8256+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:27.72569+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.299605ms 2023-04-29T13:40:27.72582+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:27.82415+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.162403ms 2023-04-29T13:40:27.82422+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:30.23501+08:00 INFO [359133,ccf50cdbcd7543d2] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=ccf50cdbcd7543d2, body=] 2023-04-29T13:40:30.23519+08:00 INFO [359133,4c618459f26cf16a] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=4c618459f26cf16a, body=] 2023-04-29T13:40:30.23584+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:40:30.23589+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:40:30.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.2371+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23712+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23713+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23715+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23716+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23717+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23718+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.2372+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23723+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23727+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23737+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23745+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23747+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23748+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23749+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23752+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23753+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23756+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23757+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.2376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23761+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23765+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23769+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23778+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23786+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23791+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23797+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23801+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23816+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23817+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23818+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23819+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23823+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23829+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.2383+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23832+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23833+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23834+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23835+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23837+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.2384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23841+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23844+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23846+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23853+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.2386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23862+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23924+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23927+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23929+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.2393+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23932+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23933+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23935+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23936+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23939+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.2394+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23942+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23943+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23945+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23946+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23948+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23949+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.2395+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23951+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23953+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23954+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23955+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23957+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23958+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23959+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23961+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23962+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23963+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23965+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23966+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.23967+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.23969+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:30.2397+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:30.24775+08:00 INFO [359133,6c8e235d30d7c912] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=6c8e235d30d7c912, body=] 2023-04-29T13:40:32.72664+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.858713ms 2023-04-29T13:40:32.72671+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:32.8243+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.288504ms 2023-04-29T13:40:32.82436+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:37.7265+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.214304ms 2023-04-29T13:40:37.72656+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:37.82487+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.9144ms 2023-04-29T13:40:37.82493+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:42.72844+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.302733ms 2023-04-29T13:40:42.72851+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:42.82524+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.832213ms 2023-04-29T13:40:42.8253+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:45.23524+08:00 INFO [359133,f2e92789b85be1a6] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=f2e92789b85be1a6, body=] 2023-04-29T13:40:45.23546+08:00 INFO [359133,174f7280df58b580] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=174f7280df58b580, body=] 2023-04-29T13:40:45.23606+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:40:45.23609+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:40:45.23699+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23702+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23704+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23705+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23707+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23708+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23709+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23711+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23715+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23718+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23719+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23721+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23722+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23723+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23727+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23736+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23739+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.2376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23761+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23765+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23767+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23768+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23769+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23771+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23772+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23775+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23776+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23777+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23778+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.2378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23786+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23788+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23793+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23797+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23801+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23804+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23815+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23817+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23818+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23819+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23829+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.2383+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23831+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23833+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23834+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23838+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23839+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23888+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23891+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23892+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23894+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23895+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23896+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23898+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23901+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23903+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23904+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23905+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23907+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23908+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23909+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23911+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23912+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23913+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23915+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23916+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23917+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23918+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.2392+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23921+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23922+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23924+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23925+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23926+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.23928+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23929+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.2393+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:40:45.23931+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:40:45.24814+08:00 INFO [359133,0ac933167502cec1] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=0ac933167502cec1, body=] 2023-04-29T13:40:47.72595+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.530308ms 2023-04-29T13:40:47.72602+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:47.82555+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.488522ms 2023-04-29T13:40:47.82562+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:52.7515+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.317262ms 2023-04-29T13:40:52.75158+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:52.83206+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.646224ms 2023-04-29T13:40:52.83213+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:57.72693+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.515408ms 2023-04-29T13:40:57.72699+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:40:57.8249+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.166203ms 2023-04-29T13:40:57.82497+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:00.23573+08:00 INFO [359133,3b17554e68864b02] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=3b17554e68864b02, body=] 2023-04-29T13:41:00.23595+08:00 INFO [359133,3d5898ad9241791d] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=3d5898ad9241791d, body=] 2023-04-29T13:41:00.23654+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:41:00.23662+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:41:00.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23784+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23786+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23788+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.2379+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23791+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23793+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23796+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23797+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23799+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.238+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23801+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23803+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23804+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23816+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23817+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23818+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23823+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23827+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23829+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.2383+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23831+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23838+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23846+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23851+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23852+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23854+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23865+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23867+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23869+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23872+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23873+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23874+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23876+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23877+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23878+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.2388+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23881+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23882+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23884+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23885+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23886+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23888+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23889+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.2389+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23892+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23893+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23894+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23896+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23897+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23898+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23901+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23902+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23904+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23905+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23907+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23908+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.2391+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23911+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23912+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23913+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23915+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23916+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23918+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23919+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.2392+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23926+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23928+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23929+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.2393+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23932+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23938+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.2394+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23941+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23943+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23948+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23949+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23951+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23952+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23953+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23955+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23961+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23962+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.23964+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.23965+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.24012+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.24015+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.24017+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.24019+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.24021+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.24022+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.24025+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.24027+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.24028+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.24029+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.24031+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.24032+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.24033+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.24035+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.24036+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.24039+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.24041+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.24042+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.24048+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.2405+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.24051+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.24053+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.24054+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.2406+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.24067+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.24068+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.24069+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.24071+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.24072+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.24074+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.24075+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:00.24076+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:00.24668+08:00 INFO [359133,54041c68eef92370] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=54041c68eef92370, body=] 2023-04-29T13:41:02.72975+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.599552ms 2023-04-29T13:41:02.72983+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:02.82523+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.819013ms 2023-04-29T13:41:02.8253+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:07.73192+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.55368ms 2023-04-29T13:41:07.73199+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:07.82469+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.257904ms 2023-04-29T13:41:07.82475+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:12.72667+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.004415ms 2023-04-29T13:41:12.72673+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:12.82493+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.607209ms 2023-04-29T13:41:12.82499+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:15.23503+08:00 INFO [359133,a585711954290b40] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=a585711954290b40, body=] 2023-04-29T13:41:15.24189+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24196+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24198+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24201+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24203+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24204+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24206+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24208+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24218+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.2422+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24227+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24229+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.2423+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24251+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24254+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24255+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24269+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24278+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.2428+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24282+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24284+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24285+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24287+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24288+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.2429+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24292+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24294+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24296+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24297+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24299+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.243+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24302+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.2436+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24362+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24368+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24382+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24388+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24402+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24426+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24428+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24429+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24438+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24441+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24442+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24457+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.2446+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24462+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24464+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24466+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24468+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.2448+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24482+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24484+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24499+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24504+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24506+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24508+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24509+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24511+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24512+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24518+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.2452+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24535+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24544+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24558+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.2456+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24568+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.2457+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24572+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24578+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24587+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24594+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24597+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.246+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24602+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24603+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24605+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24606+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24607+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.2461+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24612+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24621+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24642+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24651+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24654+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24655+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24662+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24664+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24694+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.247+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24702+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24707+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24711+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24718+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24723+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.24727+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.24747+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.25143+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.25152+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.25156+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.25157+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.25165+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.25167+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.25174+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.25179+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.25181+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.25183+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.25189+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.25195+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.25197+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.25204+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.25209+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.25211+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.25213+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.25218+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.2522+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.25221+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.25223+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.25225+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.25227+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.25229+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.2524+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.25243+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.25244+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.25246+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.25247+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.25249+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.2525+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:15.25252+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:15.25376+08:00 INFO [359133,0d0ed64ff550b02e] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=0d0ed64ff550b02e, body=] 2023-04-29T13:41:15.25509+08:00 INFO [359133,1bc2fae3501c32f6] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=1bc2fae3501c32f6, body=] 2023-04-29T13:41:15.25544+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:41:15.25548+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:41:17.72626+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.915513ms 2023-04-29T13:41:17.72633+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:17.82528+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.388606ms 2023-04-29T13:41:17.82534+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:22.72565+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.291205ms 2023-04-29T13:41:22.72571+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:22.82572+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.669325ms 2023-04-29T13:41:22.82578+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:27.72635+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.415606ms 2023-04-29T13:41:27.72643+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:27.82547+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.62491ms 2023-04-29T13:41:27.82553+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:30.23491+08:00 INFO [359133,a98c1300630c2d08] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=a98c1300630c2d08, body=] 2023-04-29T13:41:30.23584+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23588+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.2359+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23591+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23593+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23594+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23596+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23597+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23598+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.236+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23601+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23602+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23604+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23605+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23606+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23608+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23609+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.2361+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23611+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23614+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23615+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23617+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23618+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23619+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23621+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23622+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23623+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23625+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23626+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23627+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23629+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.2363+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23632+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23634+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23635+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23638+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.2364+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23641+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23642+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23644+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23645+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23646+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23648+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23649+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23651+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23652+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23653+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23655+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23656+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23657+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23659+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.2366+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23661+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23662+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23664+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23665+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23666+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23669+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.2367+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23671+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23673+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23674+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23675+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23677+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23678+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23679+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23681+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23682+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23683+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23685+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23686+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23687+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23689+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.2369+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23691+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23692+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23694+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23695+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23696+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23698+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23699+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23702+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23706+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23707+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23711+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23718+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23719+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23721+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23722+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23778+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23783+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23784+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23786+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23793+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23798+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23802+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23806+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.2381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23812+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23813+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:30.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:30.23933+08:00 INFO [359133,b8692ac72b688d86] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=b8692ac72b688d86, body=] 2023-04-29T13:41:30.23948+08:00 INFO [359133,f7f606e5fa6e6277] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=f7f606e5fa6e6277, body=] 2023-04-29T13:41:30.24025+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:41:30.24028+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:41:32.72644+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.450807ms 2023-04-29T13:41:32.7265+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:32.82795+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.855556ms 2023-04-29T13:41:32.82802+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:37.726+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.312805ms 2023-04-29T13:41:37.72606+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:37.82526+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.68151ms 2023-04-29T13:41:37.82532+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:42.72642+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.209003ms 2023-04-29T13:41:42.7265+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:42.82578+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.940514ms 2023-04-29T13:41:42.82585+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:45.23498+08:00 INFO [359133,5427e93e0d1221c1] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=5427e93e0d1221c1, body=] 2023-04-29T13:41:45.23518+08:00 INFO [359133,790b6f480dae69ab] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=790b6f480dae69ab, body=] 2023-04-29T13:41:45.23602+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23606+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23609+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23612+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23618+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.2362+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23621+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23623+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23624+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23626+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23628+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23629+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.2363+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23632+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23633+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23635+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23636+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23637+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.2364+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23642+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23643+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23644+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23646+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23647+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23648+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.2365+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23654+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23657+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23658+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23659+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23661+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23662+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23663+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23665+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23666+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23667+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23668+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.2367+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23671+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23673+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23675+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23676+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23677+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23679+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.2368+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23698+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23699+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23701+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23725+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23727+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23729+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.2373+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23734+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23739+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23741+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23745+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23746+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.2375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23754+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23758+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23759+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.2376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23761+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23766+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23828+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23834+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23838+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.2384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23841+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23853+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23857+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.2386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23864+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23865+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23867+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23869+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23871+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23872+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23874+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:41:45.23875+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:41:45.23959+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:41:45.23963+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:41:45.25112+08:00 INFO [359133,e1c948cec9403952] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=e1c948cec9403952, body=] 2023-04-29T13:41:47.73066+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.212576ms 2023-04-29T13:41:47.73145+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:47.82506+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.65541ms 2023-04-29T13:41:47.82515+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:52.74019+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.169076ms 2023-04-29T13:41:52.74026+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:52.8412+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.497781ms 2023-04-29T13:41:52.84141+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:57.72709+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.745711ms 2023-04-29T13:41:57.72715+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:41:57.82561+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.701311ms 2023-04-29T13:41:57.82567+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:00.23568+08:00 INFO [359133,ed997643dca9a089] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=ed997643dca9a089, body=] 2023-04-29T13:42:00.2367+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23676+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23686+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23689+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.2369+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23692+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23694+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23697+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23698+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23701+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23725+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23728+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23729+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.2373+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23733+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23734+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23737+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.2374+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23741+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23743+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23744+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23754+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23758+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23759+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.2376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23761+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23777+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23782+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23784+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23785+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23789+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23793+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23812+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23813+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23816+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23819+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.2382+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23821+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23823+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23824+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23825+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23827+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23828+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23829+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23831+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23918+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23923+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23926+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23927+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23929+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.2393+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23932+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23933+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23935+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23936+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23938+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.2394+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23941+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23942+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23944+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23945+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23946+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23948+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23949+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.2395+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23952+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23953+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23954+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23956+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23957+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23959+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.2396+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23962+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23963+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23964+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.23966+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:00.23967+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:00.24103+08:00 INFO [359133,732c43563db4d350] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=732c43563db4d350, body=] 2023-04-29T13:42:00.24116+08:00 INFO [359133,36296942a9ec2a78] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=36296942a9ec2a78, body=] 2023-04-29T13:42:00.24197+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:42:00.24201+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:42:02.7272+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.892514ms 2023-04-29T13:42:02.72726+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:02.82477+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.359506ms 2023-04-29T13:42:02.82484+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:07.72672+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.386606ms 2023-04-29T13:42:07.7268+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:07.82466+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.225804ms 2023-04-29T13:42:07.82474+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:12.72677+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.423206ms 2023-04-29T13:42:12.72684+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:12.82464+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.285405ms 2023-04-29T13:42:12.82471+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:15.2351+08:00 INFO [359133,535d6f3aacff249d] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=535d6f3aacff249d, body=] 2023-04-29T13:42:15.23524+08:00 INFO [359133,fa5e028780f6aecc] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=fa5e028780f6aecc, body=] 2023-04-29T13:42:15.23639+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23645+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23647+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23649+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.2365+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23651+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23653+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23654+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23655+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23657+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23658+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23661+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23662+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23664+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23665+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23667+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23668+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23669+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.2367+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23672+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23674+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23675+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23677+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23678+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23679+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23681+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23682+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23683+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23684+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23686+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23687+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23688+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23689+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23691+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23692+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23694+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23695+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23696+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23697+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23699+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23701+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23721+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23722+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23727+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23732+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23736+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23739+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.2374+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23741+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23743+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23744+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23747+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23752+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23756+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23757+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.2376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23762+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23765+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23769+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.2377+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23773+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23777+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23778+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23781+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23833+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23834+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23839+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.2384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23846+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.2385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23857+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23858+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.2386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23862+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23864+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23865+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23867+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23868+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.2387+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23871+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23873+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23874+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23875+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23882+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23885+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23886+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23888+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:15.23889+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:15.23965+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:42:15.23969+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:42:15.24952+08:00 INFO [359133,8a9d89e6d613af24] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=8a9d89e6d613af24, body=] 2023-04-29T13:42:17.72702+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.625009ms 2023-04-29T13:42:17.72709+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:17.82499+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.333805ms 2023-04-29T13:42:17.82506+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:22.72794+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.991829ms 2023-04-29T13:42:22.728+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:22.82469+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.463507ms 2023-04-29T13:42:22.82475+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:27.72624+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.224204ms 2023-04-29T13:42:27.7263+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:27.82565+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.802812ms 2023-04-29T13:42:27.82571+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:30.23509+08:00 INFO [359133,27ffb246f5a2e545] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=27ffb246f5a2e545, body=] 2023-04-29T13:42:30.23883+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23889+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23891+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23893+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23897+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23899+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.239+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23902+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23903+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23905+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23906+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23908+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23909+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23911+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23913+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23914+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23916+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23919+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23921+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23922+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23924+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23925+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23927+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23928+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.2393+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23931+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23933+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23934+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23936+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23939+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23941+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23943+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23944+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23946+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23948+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23949+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23951+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23953+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23954+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23956+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23957+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23962+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23965+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23967+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23968+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23971+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23972+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23974+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23975+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23977+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23979+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23981+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23984+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23985+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23987+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23988+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.2399+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23991+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23993+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23995+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.23997+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.23998+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24001+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24003+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24004+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24006+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24007+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24009+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.2401+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24012+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24013+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24015+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24017+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24018+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.2402+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24021+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24023+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24024+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24026+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24027+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24029+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.2403+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24032+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24034+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24035+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24037+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.2404+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24042+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24044+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24045+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24047+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24049+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.2405+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24052+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24053+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24055+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24056+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24058+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24064+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24065+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24067+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24242+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24246+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24248+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.2425+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24252+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24253+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24255+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24256+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24258+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24264+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24266+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24269+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.2427+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24272+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24273+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24275+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.2428+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24282+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24284+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24286+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24287+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24289+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24291+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24292+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24294+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24295+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24297+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24298+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.243+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24301+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24303+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:30.24305+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:30.24389+08:00 INFO [359133,623677d002ae9adf] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=623677d002ae9adf, body=] 2023-04-29T13:42:30.24497+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:42:30.24501+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:42:30.25053+08:00 INFO [359133,ab17e3bcd5d1785e] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=ab17e3bcd5d1785e, body=] 2023-04-29T13:42:32.72686+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.548408ms 2023-04-29T13:42:32.72694+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:32.82522+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.262104ms 2023-04-29T13:42:32.82528+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:37.72648+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.67481ms 2023-04-29T13:42:37.72658+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:37.82512+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.474407ms 2023-04-29T13:42:37.82518+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:42.7265+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.429606ms 2023-04-29T13:42:42.72657+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:42.82448+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.255405ms 2023-04-29T13:42:42.82455+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:45.23526+08:00 INFO [359133,12266259a0d4e23c] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=12266259a0d4e23c, body=] 2023-04-29T13:42:45.23595+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:42:45.23599+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:42:45.24079+08:00 INFO [359133,8ae43a6207796417] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=8ae43a6207796417, body=] 2023-04-29T13:42:45.24131+08:00 INFO [359133,6b099f016d1b94c2] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=6b099f016d1b94c2, body=] 2023-04-29T13:42:45.24508+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24513+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24515+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24518+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24519+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24521+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24523+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24525+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24527+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24528+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.2453+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24532+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24533+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24535+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24536+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24539+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24541+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24542+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24544+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24545+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24548+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24549+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24551+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24553+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24555+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24556+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24558+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24562+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24564+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24565+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24567+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24569+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.2457+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24572+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24573+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24575+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24576+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24578+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24579+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24581+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24583+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24584+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24586+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24587+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24589+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.2459+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24592+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24594+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24595+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24597+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24598+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.246+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24602+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24604+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24606+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24607+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.2461+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24617+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24618+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24621+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24623+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24624+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24626+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24627+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24629+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.2463+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24632+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24633+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24635+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24636+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.2464+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24641+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24643+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24645+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24646+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24648+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24649+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24651+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24652+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24654+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24657+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24658+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.2466+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24661+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24663+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24665+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24667+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.2467+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24671+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24673+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24674+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24676+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24677+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24679+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.2468+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24682+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24683+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24685+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24686+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24688+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24689+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24861+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24863+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24865+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24867+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24869+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.2487+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24872+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24873+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24875+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24876+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24878+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24879+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24881+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24882+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24884+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24885+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24887+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24889+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.2489+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24892+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24893+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24895+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24897+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24898+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.249+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24901+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24903+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24905+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:45.24906+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:42:45.24908+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:42:47.72589+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.486008ms 2023-04-29T13:42:47.72596+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:47.82703+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.288734ms 2023-04-29T13:42:47.8271+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:52.75176+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.611467ms 2023-04-29T13:42:52.75184+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:52.82464+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.355705ms 2023-04-29T13:42:52.8247+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:57.72636+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.544608ms 2023-04-29T13:42:57.72646+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:42:57.8245+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.252604ms 2023-04-29T13:42:57.82457+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:00.23493+08:00 INFO [359133,487e04f5a294f94e] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=487e04f5a294f94e, body=] 2023-04-29T13:43:00.23513+08:00 INFO [359133,d88eb027e060ab98] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=d88eb027e060ab98, body=] 2023-04-29T13:43:00.23604+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23609+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23611+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23613+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23614+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23615+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23618+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23619+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.2362+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23622+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23623+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23624+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23626+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23627+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23628+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23629+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23631+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23632+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23633+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23635+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23636+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23639+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.2364+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23642+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23643+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23644+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23645+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23647+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23648+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23649+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23651+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23652+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23656+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23657+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23659+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.2366+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23661+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23662+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23664+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23665+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23667+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23669+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23675+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23676+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23678+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23679+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23681+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23682+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23683+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23685+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23686+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23687+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23689+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.2369+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23697+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23698+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23701+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23707+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23711+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23718+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23725+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23728+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23729+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.2373+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23733+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23734+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.2374+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23741+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23745+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23746+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23749+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.2375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23753+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23754+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23756+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23757+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23758+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.2376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23811+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23821+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23823+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23824+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23827+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23828+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23829+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23831+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23835+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23839+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.2384+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23842+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23843+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23844+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23846+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23847+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23848+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23849+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23851+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23852+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23853+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23855+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23856+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:00.23857+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:00.23942+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:43:00.23946+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:43:00.24514+08:00 INFO [359133,f152709d4f110e6c] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=f152709d4f110e6c, body=] 2023-04-29T13:43:02.72615+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.389706ms 2023-04-29T13:43:02.72622+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:02.82423+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.249404ms 2023-04-29T13:43:02.8243+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:07.7259+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.198103ms 2023-04-29T13:43:07.72597+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:07.82716+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.73904ms 2023-04-29T13:43:07.82723+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:12.72672+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.308205ms 2023-04-29T13:43:12.72679+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:12.82475+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.284204ms 2023-04-29T13:43:12.82482+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:15.23567+08:00 INFO [359133,19d56eb41713c54e] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=19d56eb41713c54e, body=] 2023-04-29T13:43:15.23633+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:43:15.23636+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:43:15.24334+08:00 INFO [359133,e99df50670f3ffab] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=e99df50670f3ffab, body=] 2023-04-29T13:43:15.24427+08:00 INFO [359133,e741a2b56d06a563] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=e741a2b56d06a563, body=] 2023-04-29T13:43:15.24655+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24661+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24663+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24664+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24666+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24669+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24671+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24673+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24674+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24676+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24677+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24679+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24681+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24682+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24684+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24686+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24687+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24689+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.2469+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24692+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24694+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24695+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24697+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.247+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24702+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24705+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24707+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24708+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.2471+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24715+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24717+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24718+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.2472+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24723+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24724+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24727+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24749+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.2475+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24752+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24753+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.2476+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24761+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24766+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24767+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.2479+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24792+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24793+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24795+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24798+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.248+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24811+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.2482+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24823+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24829+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24834+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24844+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24846+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24853+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24856+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24858+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.2487+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24872+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24958+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24962+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24964+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24965+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24967+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24968+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24969+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24971+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24972+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24973+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24975+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24976+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24977+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24978+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.2498+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24981+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24982+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24984+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24985+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24986+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24987+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24989+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.2499+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24991+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24993+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24994+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24995+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24996+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.24998+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.24999+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:15.25001+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:15.25002+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:17.7259+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.291605ms 2023-04-29T13:43:17.72597+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:17.82485+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.298905ms 2023-04-29T13:43:17.82496+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:22.72568+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.072301ms 2023-04-29T13:43:22.72575+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:22.82501+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.503208ms 2023-04-29T13:43:22.82508+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:27.72597+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.851899ms 2023-04-29T13:43:27.72603+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:27.82465+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.037401ms 2023-04-29T13:43:27.82471+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:30.23527+08:00 INFO [359133,e8357736f0932087] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=e8357736f0932087, body=] 2023-04-29T13:43:30.23617+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23621+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23623+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23624+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23626+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23627+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23628+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.2363+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23631+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23632+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23634+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23635+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23636+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23639+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.2364+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23642+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23643+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23644+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23646+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23647+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23648+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.2365+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23651+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23652+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23654+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23655+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23656+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23657+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23659+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.2366+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23661+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23663+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23664+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23666+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23667+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23669+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.2367+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23671+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23673+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23674+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23675+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23677+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23678+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23679+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23681+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23682+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23683+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23685+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23686+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23687+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23689+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.2369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23691+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23693+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23694+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23697+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23698+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23699+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23701+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23703+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23711+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23714+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23715+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23721+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23722+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23737+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23739+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23743+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23747+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23752+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23806+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23816+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23817+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23825+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23835+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23838+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.2384+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23841+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23846+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23847+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.2385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23851+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:30.23853+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:30.23976+08:00 INFO [359133,200a4508c26db8bb] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=200a4508c26db8bb, body=] 2023-04-29T13:43:30.23989+08:00 INFO [359133,f827f09f3aebd86a] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=f827f09f3aebd86a, body=] 2023-04-29T13:43:30.24082+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:43:30.24086+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:43:32.7284+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.401835ms 2023-04-29T13:43:32.72847+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:32.82553+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.34572ms 2023-04-29T13:43:32.82559+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:37.72665+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.514608ms 2023-04-29T13:43:37.72672+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:37.82482+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.320805ms 2023-04-29T13:43:37.82489+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:42.72645+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.388707ms 2023-04-29T13:43:42.72652+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:42.82441+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.427007ms 2023-04-29T13:43:42.82448+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:45.23503+08:00 INFO [359133,505506d817eef5a4] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=505506d817eef5a4, body=] 2023-04-29T13:43:45.23595+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23599+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.236+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23602+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23603+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23605+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23606+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23607+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23609+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.2361+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23611+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23613+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23614+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23615+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23617+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23618+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23619+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.2362+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23622+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23623+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23625+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23626+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23627+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23629+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.2363+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23632+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23633+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23634+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23635+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23638+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.2364+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23641+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23643+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23648+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.2365+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23651+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23652+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23654+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23655+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23656+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23657+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23659+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.2366+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23661+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23663+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23664+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23665+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23667+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23668+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23669+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23671+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23672+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23673+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23675+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23676+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23677+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23678+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.2368+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23681+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23682+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23683+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23685+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23686+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23688+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23689+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.2369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23692+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23693+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23694+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23696+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23697+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23699+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23702+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23705+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23706+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23707+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23709+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.2371+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23711+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23714+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23715+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23717+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23718+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23725+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23727+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.2373+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23733+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23734+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23737+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.2374+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23741+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23791+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23793+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23794+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23798+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23799+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23802+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23803+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23806+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23807+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.2381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23811+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23813+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23816+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23826+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23829+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:43:45.23831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:43:45.2394+08:00 INFO [359133,ce504a9ad4064d3b] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=ce504a9ad4064d3b, body=] 2023-04-29T13:43:45.23953+08:00 INFO [359133,c7d8869a74beb5c7] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=c7d8869a74beb5c7, body=] 2023-04-29T13:43:45.24023+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:43:45.24026+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:43:47.72666+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.313005ms 2023-04-29T13:43:47.72672+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:47.82485+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.68291ms 2023-04-29T13:43:47.82497+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:52.73862+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.644109ms 2023-04-29T13:43:52.73876+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:52.82457+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.537809ms 2023-04-29T13:43:52.82464+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:57.72682+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.67921ms 2023-04-29T13:43:57.72699+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:43:57.82485+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.503108ms 2023-04-29T13:43:57.82491+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:00.23509+08:00 INFO [359133,36d44de8cb65c03f] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=36d44de8cb65c03f, body=] 2023-04-29T13:44:00.23529+08:00 INFO [359133,ab9deb99566aa025] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=ab9deb99566aa025, body=] 2023-04-29T13:44:00.23592+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:44:00.23596+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:44:00.2368+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23684+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23685+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23687+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23688+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.2369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23691+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23692+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23694+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23696+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23698+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23699+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.237+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23703+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23704+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23705+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23707+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23708+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23709+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23711+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23715+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23718+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23719+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.2372+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23722+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23723+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23724+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23727+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23728+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23729+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23732+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23733+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23734+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23736+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23737+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23739+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23741+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23746+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23749+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.2375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23754+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23757+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23758+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23759+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.2376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23762+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23765+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23766+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23775+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23776+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23778+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23779+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23781+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23782+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23783+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23785+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23786+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23789+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23793+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23802+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23812+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23813+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23815+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23816+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.2382+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23821+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23823+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23824+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23879+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23883+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23885+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23886+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23887+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23889+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.2389+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23891+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23893+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23894+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23895+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23897+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23898+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23899+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.239+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23902+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23903+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23904+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23906+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23908+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23909+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.2391+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23911+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23913+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23914+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23915+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23917+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23918+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.2392+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23921+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.23923+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:00.23924+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:00.24589+08:00 INFO [359133,972599b87639149a] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=972599b87639149a, body=] 2023-04-29T13:44:02.72598+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.301705ms 2023-04-29T13:44:02.72605+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:02.82507+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.364905ms 2023-04-29T13:44:02.82513+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:07.72658+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.549508ms 2023-04-29T13:44:07.72664+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:07.82628+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.490922ms 2023-04-29T13:44:07.82634+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:12.72657+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.839612ms 2023-04-29T13:44:12.72663+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:12.82489+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.607709ms 2023-04-29T13:44:12.82495+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:15.23503+08:00 INFO [359133,1e98247af36a380f] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=1e98247af36a380f, body=] 2023-04-29T13:44:15.23602+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23606+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23608+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23613+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23615+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23617+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23618+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23619+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23621+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23622+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23624+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23625+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23626+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23628+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23629+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.2363+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23632+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23633+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23634+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23636+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23638+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23641+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23642+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23644+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23645+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23646+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23648+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23649+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.2365+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23652+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23653+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23654+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23655+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23657+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23658+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23659+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23661+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23666+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23668+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23669+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23671+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23672+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23673+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23674+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23676+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23677+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23678+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.2369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23691+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23693+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23695+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23697+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23698+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23699+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23703+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.2374+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23743+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23747+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23761+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23762+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23783+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23786+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23791+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23792+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23794+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23795+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23796+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23798+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23799+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23802+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23803+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23806+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23807+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23812+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23865+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23869+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.2387+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23872+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23873+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23874+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23876+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23877+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23879+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.2388+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23881+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23883+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23884+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23885+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23887+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23888+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23889+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23891+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23892+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23894+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23895+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23897+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23898+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23899+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23901+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23902+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23903+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23905+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23906+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23907+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.23908+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:15.23915+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:15.24039+08:00 INFO [359133,e55cf07aa1c95ffc] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=e55cf07aa1c95ffc, body=] 2023-04-29T13:44:15.24052+08:00 INFO [359133,20af96066a1e2e66] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=20af96066a1e2e66, body=] 2023-04-29T13:44:15.24131+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:44:15.24134+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:44:17.72597+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.9672ms 2023-04-29T13:44:17.72604+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:17.82496+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.249604ms 2023-04-29T13:44:17.82502+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:22.7265+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.874313ms 2023-04-29T13:44:22.72657+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:22.82504+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.572909ms 2023-04-29T13:44:22.8251+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:27.72677+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.502607ms 2023-04-29T13:44:27.72684+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:27.82512+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.65951ms 2023-04-29T13:44:27.82519+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:30.23497+08:00 INFO [359133,7f18a7d00f7d6dd6] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=7f18a7d00f7d6dd6, body=] 2023-04-29T13:44:30.23514+08:00 INFO [359133,25f1cf81c4ab8c76] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=25f1cf81c4ab8c76, body=] 2023-04-29T13:44:30.23574+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:44:30.23577+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:44:30.23678+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23683+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23685+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23686+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23688+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23689+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.2369+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23692+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23693+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23698+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.237+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23703+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23707+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23718+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23739+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23747+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23759+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.2376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23765+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23767+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23768+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.2377+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23771+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23772+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23774+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23775+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23776+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23778+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23779+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.2378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23782+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23786+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23788+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23793+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23799+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23802+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23803+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23806+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23807+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.2381+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23812+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23821+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23822+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23825+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23826+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23839+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23841+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23848+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23853+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23857+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23858+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.2386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23863+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23865+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23867+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23869+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23872+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23873+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23874+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23876+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23877+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23879+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23925+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23932+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23935+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23938+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23941+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23943+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23944+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23945+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23947+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23948+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23949+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23951+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23952+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23954+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23955+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23956+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23958+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23959+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23961+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23962+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23963+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23965+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23966+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23968+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23969+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.2397+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23972+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23973+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23974+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23976+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.23977+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:30.23978+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:30.2461+08:00 INFO [359133,8af7faaeda8b1728] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=8af7faaeda8b1728, body=] 2023-04-29T13:44:32.72769+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.928528ms 2023-04-29T13:44:32.72776+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:32.82451+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.081901ms 2023-04-29T13:44:32.82459+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:37.7267+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.363806ms 2023-04-29T13:44:37.72677+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:37.8245+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.505107ms 2023-04-29T13:44:37.82455+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:42.72592+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.493608ms 2023-04-29T13:44:42.72599+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:42.82435+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.413307ms 2023-04-29T13:44:42.82441+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:45.2347+08:00 INFO [359133,c5338087ad22405f] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=c5338087ad22405f, body=] 2023-04-29T13:44:45.2349+08:00 INFO [359133,13fc60c9e543063c] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=13fc60c9e543063c, body=] 2023-04-29T13:44:45.23558+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:44:45.23562+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:44:45.23657+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23661+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23663+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23664+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23665+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23667+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23668+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23669+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23672+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23673+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23675+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23676+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23678+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23679+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.2368+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23682+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23683+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23684+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23686+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23687+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23688+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23689+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23691+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23692+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23693+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23695+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23696+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23697+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23699+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.237+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23701+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23703+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23704+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23705+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23707+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23708+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23709+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.2371+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23712+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23713+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23715+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23716+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.2372+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23722+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23727+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23733+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23737+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23759+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.2376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23761+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23765+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23767+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23768+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23769+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23771+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23777+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.2378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23783+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23787+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23788+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23791+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23792+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23793+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23795+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23796+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23797+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23799+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.238+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23801+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23803+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23804+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23806+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23812+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23867+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23872+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23874+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23875+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23877+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23879+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23881+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23882+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23884+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23885+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23887+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23889+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.2389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23892+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23893+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23895+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23896+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23898+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23901+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23904+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23906+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23907+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23908+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.2391+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23911+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23912+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23914+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23915+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23916+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.23918+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:44:45.23919+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:44:45.24595+08:00 INFO [359133,23a8cbe6ba4c9f8d] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=23a8cbe6ba4c9f8d, body=] 2023-04-29T13:44:47.72582+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.443407ms 2023-04-29T13:44:47.72588+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:47.82453+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.225204ms 2023-04-29T13:44:47.8246+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:52.73321+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.622153ms 2023-04-29T13:44:52.73333+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:52.82834+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.187361ms 2023-04-29T13:44:52.82842+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:57.72604+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.492408ms 2023-04-29T13:44:57.7261+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:44:57.82507+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.65941ms 2023-04-29T13:44:57.82513+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:00.23848+08:00 INFO [359133,e02fa76d9e7f2b6c] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=e02fa76d9e7f2b6c, body=] 2023-04-29T13:45:00.23867+08:00 INFO [359133,5785b82bb12fdd9a] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=5785b82bb12fdd9a, body=] 2023-04-29T13:45:00.23928+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:45:00.23932+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:45:00.24034+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.2404+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24042+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24043+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.2405+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24052+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24053+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24055+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24059+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.2406+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24062+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24063+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24065+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24066+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24067+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24069+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.2407+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24071+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24073+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24074+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24075+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24076+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24078+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24079+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.2408+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24082+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24083+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24084+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24085+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24087+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24088+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24089+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24091+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24092+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24093+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24095+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24096+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24097+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24099+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.241+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24102+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24103+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24105+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24106+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24107+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24108+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.2411+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24111+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24112+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24113+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24115+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24116+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24117+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24119+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.2412+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24121+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24123+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24124+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24125+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24127+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24128+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24129+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24131+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24132+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24133+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24135+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24136+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24139+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.2414+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24142+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24149+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24151+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24152+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24154+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24155+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24156+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24158+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24159+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.2416+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24162+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24163+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24164+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24166+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24167+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24168+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24169+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24171+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24172+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24174+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24176+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24177+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24178+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24179+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24181+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24182+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24183+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24185+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24186+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24187+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24188+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.2419+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24191+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24239+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24242+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24244+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24249+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24251+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24252+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24254+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24255+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24256+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24258+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24259+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.2426+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24262+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24263+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24264+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24266+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24267+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24268+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.2427+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24271+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24272+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24273+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24275+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24276+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24277+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24279+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.2428+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24281+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24282+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24284+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24285+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:00.24286+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:00.24852+08:00 INFO [359133,7fb73619db437c54] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=7fb73619db437c54, body=] 2023-04-29T13:45:02.72877+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.385149ms 2023-04-29T13:45:02.72884+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:02.82478+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.456307ms 2023-04-29T13:45:02.82484+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:07.72582+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.151002ms 2023-04-29T13:45:07.7259+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:07.82627+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.764726ms 2023-04-29T13:45:07.82633+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:12.72613+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.506208ms 2023-04-29T13:45:12.7262+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:12.82517+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.342206ms 2023-04-29T13:45:12.82523+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:15.2365+08:00 INFO [359133,7336692abc95fc2d] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=7336692abc95fc2d, body=] 2023-04-29T13:45:15.23669+08:00 INFO [359133,ca26aecd86c56875] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=ca26aecd86c56875, body=] 2023-04-29T13:45:15.23758+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23765+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23767+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23768+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.2377+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23771+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23772+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23774+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23775+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23776+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23777+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23779+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.2378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23783+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23787+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23788+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23792+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23793+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23827+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23828+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23829+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23831+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23835+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23839+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.2384+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23842+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23843+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23844+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23846+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23847+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23848+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.2385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23851+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23852+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23854+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23855+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23856+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23857+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23859+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.2386+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23861+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23862+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23864+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23865+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23866+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23868+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23869+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23871+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23872+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23873+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23875+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23876+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23877+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23878+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.2388+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23881+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23882+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23883+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23885+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23886+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23888+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23889+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.2389+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23891+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23893+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23894+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23895+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23896+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23898+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23899+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.239+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23901+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23903+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23904+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23905+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23906+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23908+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23909+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.2391+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23911+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23961+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23965+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23966+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23968+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23969+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.2397+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23972+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23973+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23975+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23976+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23977+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23978+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.2398+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23981+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23982+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23983+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23985+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23986+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23988+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23989+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.2399+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23991+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23993+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23994+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23995+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.23997+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.23998+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.24+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.24002+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.24003+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.24005+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:15.24006+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:15.24081+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:45:15.24086+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:45:15.25372+08:00 INFO [359133,adf15f1a2b08d40a] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=adf15f1a2b08d40a, body=] 2023-04-29T13:45:17.72691+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.206518ms 2023-04-29T13:45:17.72698+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:17.82546+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.63531ms 2023-04-29T13:45:17.82552+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:22.72721+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.132016ms 2023-04-29T13:45:22.72729+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:22.82503+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.852013ms 2023-04-29T13:45:22.8251+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:27.72696+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.105216ms 2023-04-29T13:45:27.72702+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:27.82466+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.733311ms 2023-04-29T13:45:27.82472+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:30.2349+08:00 INFO [359133,30dc421fd7ed62a1] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=30dc421fd7ed62a1, body=] 2023-04-29T13:45:30.23511+08:00 INFO [359133,f8fc9ce93c901256] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=f8fc9ce93c901256, body=] 2023-04-29T13:45:30.23573+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:45:30.23578+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:45:30.23619+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.23622+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.23624+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.23625+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.23626+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.23628+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.23629+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.2363+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.23632+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.23633+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.23634+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.23636+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.23637+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.2364+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.23641+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.23643+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.23644+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.23645+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.23647+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.23648+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.23649+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.2365+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.23652+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.23653+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.23654+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.23656+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.23657+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.23658+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.23659+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.23661+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.23663+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.23664+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24015+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24019+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24022+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24023+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24024+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24026+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24027+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24028+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.2403+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24031+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24032+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24034+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24036+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24037+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24041+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24042+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24044+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24045+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24047+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24048+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24049+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24051+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24052+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24053+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24055+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24056+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24057+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24059+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.2406+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24061+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24063+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24064+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24066+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24067+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24068+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24069+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24071+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24072+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24073+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24079+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.2408+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24081+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24084+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24085+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24087+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24088+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24089+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.2409+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24092+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24093+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24094+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24095+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24097+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24098+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24099+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.241+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24102+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24103+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24104+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24105+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24107+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24108+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24109+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.2411+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24112+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24113+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24115+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24116+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24117+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24118+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.2412+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24122+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24123+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24124+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24125+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24127+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24128+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.2413+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24131+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24132+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24133+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24135+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24136+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24139+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24141+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24142+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24143+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24144+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24146+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24147+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24148+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.2415+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24151+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24152+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24154+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24155+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24156+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24157+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.2416+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24162+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24163+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:30.24164+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:30.24682+08:00 INFO [359133,f4479592e09caeab] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=f4479592e09caeab, body=] 2023-04-29T13:45:32.72656+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.182818ms 2023-04-29T13:45:32.72667+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:32.82491+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.431707ms 2023-04-29T13:45:32.82497+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:37.7271+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.681011ms 2023-04-29T13:45:37.72717+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:37.82524+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.541308ms 2023-04-29T13:45:37.8253+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:42.72629+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.442106ms 2023-04-29T13:45:42.72637+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:42.82639+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.658524ms 2023-04-29T13:45:42.82648+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:45.23575+08:00 INFO [359133,68aa814ecd1aa2fe] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=68aa814ecd1aa2fe, body=] 2023-04-29T13:45:45.23673+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23677+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23679+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.2368+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23682+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23685+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23686+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23688+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23689+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.2369+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23692+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23693+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23695+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23696+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23697+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23698+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23701+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23702+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23711+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23717+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23719+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.2372+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23722+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23737+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23739+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23743+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23747+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.2375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23751+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23769+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23772+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23773+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23775+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23777+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23783+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23794+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23804+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23821+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23822+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23825+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23826+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23832+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23833+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23854+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23857+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23859+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23862+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23941+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23956+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23959+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.2396+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23962+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23963+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23964+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23966+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23967+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23969+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.2397+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23971+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23972+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23975+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23976+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23977+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23979+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.2398+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23981+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23982+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23984+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23985+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23986+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23988+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23989+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.2399+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23991+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23993+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23995+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23996+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.23997+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:45:45.23999+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:45:45.24134+08:00 INFO [359133,562cc22b2af204ea] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=562cc22b2af204ea, body=] 2023-04-29T13:45:45.24154+08:00 INFO [359133,525d8cc476a30ad7] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=525d8cc476a30ad7, body=] 2023-04-29T13:45:45.24372+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:45:45.24376+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:45:47.72706+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.149917ms 2023-04-29T13:45:47.72713+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:47.82595+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.975015ms 2023-04-29T13:45:47.82602+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:52.73542+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.978129ms 2023-04-29T13:45:52.73549+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:52.82554+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.41042ms 2023-04-29T13:45:52.82566+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:57.73135+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.912485ms 2023-04-29T13:45:57.73143+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:45:57.82507+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.67541ms 2023-04-29T13:45:57.82514+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:00.23708+08:00 INFO [359133,e9f290570a90a5ac] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=e9f290570a90a5ac, body=] 2023-04-29T13:46:00.23727+08:00 INFO [359133,ac3568eb47ef72cb] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=ac3568eb47ef72cb, body=] 2023-04-29T13:46:00.23818+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23825+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23826+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23829+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23834+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23837+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.2384+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23841+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23846+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.2385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23853+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23854+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.2386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23862+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23864+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23866+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23872+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23873+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23875+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23876+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23878+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23879+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.2388+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23881+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23883+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23884+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23885+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23887+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23888+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23889+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23891+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23893+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23895+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23896+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23897+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23899+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23901+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23902+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23904+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23905+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23906+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23908+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23909+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23911+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23912+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23913+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23916+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23917+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23919+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.2392+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23921+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23923+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23924+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23925+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23926+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23928+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23929+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.2393+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23932+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23933+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23934+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23935+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23938+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23939+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23941+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23942+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23943+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23945+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23946+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23947+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23948+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.2395+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23951+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23952+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23954+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23955+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23957+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23958+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23959+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.2396+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23962+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23964+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23966+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23971+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.23973+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.23974+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.24024+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.24028+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.24029+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.24031+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.24032+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.24035+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.24036+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.24038+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.2404+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.24041+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.24043+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.24044+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.24045+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.24046+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.24048+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.24049+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.24051+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.24052+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.24054+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.24055+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.24058+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.24059+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.24061+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.24062+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.24063+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.24064+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.24066+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.24071+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.24073+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.24075+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.24076+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:00.24077+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:00.24178+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:46:00.24182+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:46:00.2552+08:00 INFO [359133,35a31cecf509489d] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=35a31cecf509489d, body=] 2023-04-29T13:46:02.72631+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.741711ms 2023-04-29T13:46:02.72639+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:02.82511+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.848413ms 2023-04-29T13:46:02.82519+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:07.72793+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.666425ms 2023-04-29T13:46:07.72802+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:07.82623+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.482321ms 2023-04-29T13:46:07.82633+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:12.72684+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.104016ms 2023-04-29T13:46:12.72693+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:12.82627+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.629924ms 2023-04-29T13:46:12.82633+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:15.23512+08:00 INFO [359133,de5abd2fd2bf7fe4] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=de5abd2fd2bf7fe4, body=] 2023-04-29T13:46:15.23535+08:00 INFO [359133,8b1c73738cd4584a] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=8b1c73738cd4584a, body=] 2023-04-29T13:46:15.23621+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23625+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23627+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23628+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.2363+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23631+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23632+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23634+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23635+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23636+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23639+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23641+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23642+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23643+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23645+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23646+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23647+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23649+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.2365+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23652+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23654+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23655+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23656+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23657+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23659+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.2366+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23661+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23663+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23664+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23665+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23667+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23669+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23671+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23672+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23673+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23675+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23676+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23677+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23678+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.2368+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23681+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23682+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23684+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23685+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23686+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23687+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23693+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23695+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23696+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23697+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23699+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23702+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23706+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23709+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23711+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23713+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23715+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23718+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23719+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23721+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23722+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23723+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23724+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.2373+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23738+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.2375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23759+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.2376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23765+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23768+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23769+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23771+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23822+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23827+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23828+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.2383+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23831+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23834+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23835+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23837+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23839+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23841+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23842+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23843+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23846+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23847+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23853+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23857+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23858+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.2386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23862+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23864+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23865+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23866+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23868+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:15.23869+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:15.23974+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:46:15.23978+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:46:15.25173+08:00 INFO [359133,727e1f6a7875bedf] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=727e1f6a7875bedf, body=] 2023-04-29T13:46:17.72664+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.67231ms 2023-04-29T13:46:17.72674+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:17.82543+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.805213ms 2023-04-29T13:46:17.82549+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:22.73088+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.979172ms 2023-04-29T13:46:22.73103+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:22.82663+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.989429ms 2023-04-29T13:46:22.82674+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:27.72724+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.097316ms 2023-04-29T13:46:27.72731+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:27.82556+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.403221ms 2023-04-29T13:46:27.82567+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:30.23677+08:00 INFO [359133,407219a044575434] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=407219a044575434, body=] 2023-04-29T13:46:30.23697+08:00 INFO [359133,c7e3d7922f1c3d49] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=c7e3d7922f1c3d49, body=] 2023-04-29T13:46:30.2379+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23797+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.238+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23801+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23802+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23813+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23816+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23822+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23825+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23826+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23829+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23834+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23837+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.2384+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23841+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23843+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23844+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23845+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23847+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23848+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23849+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23851+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23852+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23853+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23856+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23857+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.2386+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23861+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23862+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23864+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23865+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23873+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23875+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23876+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23878+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23879+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.2388+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23882+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23883+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23885+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23887+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23889+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.2389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23891+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23892+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23894+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23895+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23896+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23898+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23899+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23901+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23903+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23904+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23906+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23907+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23908+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.2391+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23911+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23914+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23915+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23917+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23918+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23919+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23921+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23922+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23924+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23925+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23926+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23928+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23929+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.2393+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23932+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23933+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23935+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23936+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23939+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.2394+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23942+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23943+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23944+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23945+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23947+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23948+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.23949+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.23951+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.24012+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.24015+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.24017+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.24018+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.24019+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.24021+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.24022+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.24024+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.24025+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.24026+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.24028+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.24029+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.2403+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.24033+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.24034+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.24036+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.24038+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.2404+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.24042+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.24043+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.24044+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.24046+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.24047+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.24048+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.2405+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.24051+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.24052+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.24053+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.24055+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.24056+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.24057+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:30.24059+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:30.24183+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:46:30.24187+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:46:30.25881+08:00 INFO [359133,ce95bdc5d134940c] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=ce95bdc5d134940c, body=] 2023-04-29T13:46:32.72735+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.016015ms 2023-04-29T13:46:32.72743+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:32.82609+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.132417ms 2023-04-29T13:46:32.82616+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:37.72833+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.998029ms 2023-04-29T13:46:37.72848+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:37.82572+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.754726ms 2023-04-29T13:46:37.82584+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:42.72743+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.199418ms 2023-04-29T13:46:42.72751+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:42.82635+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.40822ms 2023-04-29T13:46:42.82644+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:45.23642+08:00 INFO [359133,8231e516f747e4dc] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=8231e516f747e4dc, body=] 2023-04-29T13:46:45.23747+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:46:45.23751+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:46:45.24602+08:00 INFO [359133,83d1b7735c93e644] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=83d1b7735c93e644, body=] 2023-04-29T13:46:45.24627+08:00 INFO [359133,821ac41634ff75a4] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=821ac41634ff75a4, body=] 2023-04-29T13:46:45.25192+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25196+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25198+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.252+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25201+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25202+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25204+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25206+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25207+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25209+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.2521+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25211+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25213+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25214+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25215+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25217+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25218+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25219+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25221+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25222+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25223+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25225+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25226+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25227+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25234+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25236+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25238+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.2524+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25241+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25243+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25244+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25245+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25247+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25248+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25249+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25251+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25252+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25253+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25255+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25256+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25258+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25259+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.2526+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25262+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25263+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25264+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25266+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25267+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25268+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25269+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25271+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25272+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25274+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25275+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25276+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25278+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25279+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.2528+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25281+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25283+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25284+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25285+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25287+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25288+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25289+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.2529+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25292+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25293+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25294+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25296+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25297+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25298+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.253+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25301+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25302+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25304+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25305+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25307+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25308+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25309+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25311+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25312+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25313+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25315+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25316+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25317+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25319+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.2532+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25321+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25323+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25324+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25325+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25327+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25333+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25335+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25337+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.2534+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25341+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25342+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25344+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25345+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25346+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25395+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25398+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25399+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25401+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25402+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25405+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25406+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25407+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25409+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.2541+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25411+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25413+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25414+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25415+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25417+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25418+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.2542+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25421+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25422+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25423+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25425+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25426+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25427+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25433+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25434+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25436+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25439+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.2544+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25441+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25443+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:45.25444+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:46:45.25445+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:46:47.72708+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.943114ms 2023-04-29T13:46:47.72717+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:47.82591+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.027415ms 2023-04-29T13:46:47.82599+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:52.73772+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.39292ms 2023-04-29T13:46:52.73788+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:52.82628+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.258033ms 2023-04-29T13:46:52.82636+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:57.72647+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.957914ms 2023-04-29T13:46:57.72655+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:46:57.82533+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.861613ms 2023-04-29T13:46:57.82541+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:00.23494+08:00 INFO [359133,5b1e184297db2c6b] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=5b1e184297db2c6b, body=] 2023-04-29T13:47:00.23581+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23586+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23587+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23598+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23601+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23602+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23604+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23605+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23607+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23609+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.2361+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23611+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23613+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23614+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23615+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23617+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23618+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23619+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.2362+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23622+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23623+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23624+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23625+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23627+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23628+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23629+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23634+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23636+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23639+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.2364+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23642+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23643+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23644+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23646+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23648+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23649+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.2365+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23652+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23653+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23654+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23656+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23657+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23659+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.2366+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23661+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23663+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23664+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23665+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23667+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23669+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.2367+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23672+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23673+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23674+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23677+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23678+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23679+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23681+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23682+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23683+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23685+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23686+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23689+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23694+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23696+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23697+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23699+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.237+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23701+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23704+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23705+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23708+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.2371+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23711+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23714+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23716+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23718+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23719+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.2372+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23722+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23729+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23738+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.238+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23816+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.2382+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23822+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23826+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23832+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23834+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23839+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23841+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23845+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:00.23846+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:00.23966+08:00 INFO [359133,d43d6db9a48bb530] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=d43d6db9a48bb530, body=] 2023-04-29T13:47:00.23979+08:00 INFO [359133,cf1c4ab7349e02dc] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=cf1c4ab7349e02dc, body=] 2023-04-29T13:47:00.2408+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:47:00.24084+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:47:02.72772+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.329119ms 2023-04-29T13:47:02.72783+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:02.82483+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.767212ms 2023-04-29T13:47:02.8249+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:07.72726+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.531023ms 2023-04-29T13:47:07.72733+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:07.82527+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.987315ms 2023-04-29T13:47:07.82533+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:12.72678+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.939615ms 2023-04-29T13:47:12.72685+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:12.82472+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.151203ms 2023-04-29T13:47:12.8248+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:15.24598+08:00 INFO [359133,e74f7aab36b28d33] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=e74f7aab36b28d33, body=] 2023-04-29T13:47:15.2472+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24725+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24728+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24729+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24734+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24739+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.2474+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24742+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24746+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.2475+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24753+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24756+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24759+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.2476+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24761+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24765+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24768+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24769+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.2477+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24772+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24773+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24776+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24777+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24778+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.2478+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24781+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24782+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24785+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24786+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.2479+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.248+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24802+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.2481+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24816+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24817+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.2482+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24824+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24826+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24827+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.2483+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24831+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24832+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24834+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24835+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24836+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24839+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.2484+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24845+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24846+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24847+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.2485+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.2486+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24864+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24865+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24866+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24971+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24975+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24977+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24978+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.2498+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24981+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24982+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24984+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24985+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24986+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24989+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24991+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24992+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24993+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24995+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.24996+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.24997+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.25001+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.25003+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.25009+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.25012+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.25013+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.25015+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.25016+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.25018+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.25019+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.2502+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.25021+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.25023+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.25024+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.25025+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:15.25026+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:15.25141+08:00 INFO [359133,e04fa137cebd86f9] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=e04fa137cebd86f9, body=] 2023-04-29T13:47:15.25153+08:00 INFO [359133,02f28657719e0fd1] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=02f28657719e0fd1, body=] 2023-04-29T13:47:15.25254+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:47:15.25259+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:47:17.72666+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.932314ms 2023-04-29T13:47:17.72675+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:17.82597+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.496122ms 2023-04-29T13:47:17.82603+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:22.72828+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.376935ms 2023-04-29T13:47:22.72836+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:22.82481+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.738911ms 2023-04-29T13:47:22.82491+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:27.72848+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.161832ms 2023-04-29T13:47:27.72855+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:27.82504+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.879114ms 2023-04-29T13:47:27.8251+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:30.24241+08:00 INFO [359133,899e1133df4db4ef] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=899e1133df4db4ef, body=] 2023-04-29T13:47:30.24334+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24339+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24341+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24343+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24345+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24346+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24347+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24349+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.2435+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24351+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24353+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24354+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24355+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24357+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24358+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24359+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24361+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24362+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24363+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24364+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24366+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24367+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24369+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.2437+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24374+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24375+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24376+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24377+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24379+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.2438+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24385+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24388+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24391+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24392+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24394+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24395+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24396+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24397+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24399+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.244+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24401+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24403+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24404+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24405+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24408+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24409+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.2441+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24412+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24413+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24414+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24416+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24417+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24418+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.2442+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24424+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24426+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24428+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24429+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24431+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24432+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24433+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24436+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24439+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24441+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24442+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24443+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24445+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24447+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24449+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.2445+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24457+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24459+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.2446+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24461+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24464+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24465+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24467+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24468+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.2447+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24471+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24472+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24473+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24475+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24476+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24477+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24479+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.2448+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24481+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24483+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24484+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24485+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24487+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24488+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24489+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24491+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24492+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24542+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24549+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24551+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24553+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24554+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24555+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24557+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24558+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.2456+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24561+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24564+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24565+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24567+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24568+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24569+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.2457+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24572+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24573+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24574+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24576+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24577+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24578+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.2458+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24581+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24582+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24584+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24585+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24586+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24588+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24589+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.2459+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:30.24591+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:30.24712+08:00 INFO [359133,2f1c527084c03309] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=2f1c527084c03309, body=] 2023-04-29T13:47:30.24726+08:00 INFO [359133,8b1c415c504321af] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=8b1c415c504321af, body=] 2023-04-29T13:47:30.24831+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:47:30.24835+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:47:32.72725+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.140917ms 2023-04-29T13:47:32.72731+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:32.82559+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.898114ms 2023-04-29T13:47:32.82566+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:37.7277+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.04733ms 2023-04-29T13:47:37.72783+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:37.82535+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.391221ms 2023-04-29T13:47:37.82542+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:42.72618+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.790912ms 2023-04-29T13:47:42.72629+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:42.82573+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.830113ms 2023-04-29T13:47:42.82581+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:45.23524+08:00 INFO [359133,83c07ed2c6b67923] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=83c07ed2c6b67923, body=] 2023-04-29T13:47:45.23558+08:00 INFO [359133,fda32fd2cabcb8ca] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=fda32fd2cabcb8ca, body=] 2023-04-29T13:47:45.23663+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23724+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23728+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23729+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23732+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23733+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23748+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23753+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23756+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.2376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23762+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23765+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23766+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23767+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23769+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.2377+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23773+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23774+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23778+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23779+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23789+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23797+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.238+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23801+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23803+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23804+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23816+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23818+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23819+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.2382+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23821+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23823+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23824+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23825+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23827+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23828+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23829+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.2383+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23835+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23845+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23847+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.2385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23854+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23856+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.2386+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23864+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23866+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23867+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23868+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23869+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23871+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23873+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23874+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23876+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23877+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23878+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.2388+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23881+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23882+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23884+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23885+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23887+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23888+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.2389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23891+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23892+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23893+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23895+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23951+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23955+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23957+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23959+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.2396+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23961+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23963+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23964+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23965+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23967+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23968+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23969+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23972+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23973+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23974+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23976+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23977+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23978+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23979+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23981+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23982+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23984+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23985+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23986+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23987+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23989+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.2399+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23992+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23993+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23994+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.23996+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:47:45.23997+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:47:45.24091+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:47:45.24094+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:47:45.25394+08:00 INFO [359133,ee2a683f93cbb6ef] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=ee2a683f93cbb6ef, body=] 2023-04-29T13:47:47.72684+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.755312ms 2023-04-29T13:47:47.72693+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:47.82468+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.348606ms 2023-04-29T13:47:47.82476+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:52.77104+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=33.376279ms 2023-04-29T13:47:52.77111+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:52.83099+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.179575ms 2023-04-29T13:47:52.83105+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:57.7272+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.807313ms 2023-04-29T13:47:57.72732+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:47:57.82575+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.044216ms 2023-04-29T13:47:57.82581+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:00.23498+08:00 INFO [359133,a97053f0f4fc0574] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=a97053f0f4fc0574, body=] 2023-04-29T13:48:00.23517+08:00 INFO [359133,69638a033c13602e] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=69638a033c13602e, body=] 2023-04-29T13:48:00.23611+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:48:00.23616+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:48:00.23716+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23723+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23724+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23726+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23727+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23728+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.2373+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23731+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23734+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23735+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23738+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23745+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.2375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23752+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23754+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23755+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23757+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.2376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23762+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23763+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.2377+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23771+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23773+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23774+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23777+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23778+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23781+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23782+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23783+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23786+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23787+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23789+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23803+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23806+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23807+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23812+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23815+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23816+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23818+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23819+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23823+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23824+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23827+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23828+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.2383+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23831+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23835+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23839+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.2384+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23841+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23843+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23845+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23846+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23847+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.2385+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23853+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23856+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23857+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23861+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23862+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23864+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23866+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23867+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23927+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23931+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23932+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23934+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23935+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23936+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.2394+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23941+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23942+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23944+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23945+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23946+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23947+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23949+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.2395+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23951+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23953+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23955+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23956+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23958+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23959+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.2396+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23962+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23963+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23964+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23969+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23971+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23972+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23973+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23976+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.23977+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:00.23979+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:00.25229+08:00 INFO [359133,d7ed9969e7366e8f] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=d7ed9969e7366e8f, body=] 2023-04-29T13:48:02.72708+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.131417ms 2023-04-29T13:48:02.72715+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:02.82504+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.536808ms 2023-04-29T13:48:02.82512+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:07.72647+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.456207ms 2023-04-29T13:48:07.72653+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:07.82499+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.788012ms 2023-04-29T13:48:07.82505+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:12.72736+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.062616ms 2023-04-29T13:48:12.72744+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:12.82845+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.548652ms 2023-04-29T13:48:12.82852+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:15.23843+08:00 INFO [359133,a09640b83fccb4e8] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=a09640b83fccb4e8, body=] 2023-04-29T13:48:15.23942+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.23946+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.23948+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.23949+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.23951+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.23952+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.23953+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.23956+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.23957+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.23958+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.2396+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.23961+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.23963+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.23964+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.23965+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.23966+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.23968+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.23969+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.2397+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.23972+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.23973+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.23975+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.23976+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.23978+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.23979+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.2398+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.23982+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.23983+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.23984+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.23989+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.23991+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.23992+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.23994+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.23995+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.23998+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.23999+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24001+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24002+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24004+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24005+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24006+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24008+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.2401+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24011+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24012+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24014+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24015+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24016+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24018+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24019+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.2402+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24021+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24023+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24024+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24027+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24029+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.2403+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24032+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24033+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24034+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24036+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24037+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24039+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24041+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24042+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24043+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24045+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24046+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24047+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24049+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.2405+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24051+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24052+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24054+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24055+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24056+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24058+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24059+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.2406+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24061+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24063+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24064+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24066+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24067+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24068+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.2407+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24071+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24072+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24074+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24075+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24076+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24078+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24079+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.2408+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24082+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24083+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24084+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24101+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24102+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24104+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24105+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24106+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24154+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24158+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24159+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24161+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24162+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24164+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24165+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24166+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24168+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24169+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.2417+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24172+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24173+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24174+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24175+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24177+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24178+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24179+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24181+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24182+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24184+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24185+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.2419+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24192+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24193+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24194+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24196+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24197+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24198+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.242+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24201+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:15.24202+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:15.24317+08:00 INFO [359133,01f55cce5a468a6c] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=01f55cce5a468a6c, body=] 2023-04-29T13:48:15.24329+08:00 INFO [359133,3cec7600aac29720] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=3cec7600aac29720, body=] 2023-04-29T13:48:15.24432+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:48:15.24435+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:48:17.72723+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.810112ms 2023-04-29T13:48:17.7273+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:17.82562+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.900613ms 2023-04-29T13:48:17.82569+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:22.72582+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.385406ms 2023-04-29T13:48:22.72589+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:22.83074+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.515794ms 2023-04-29T13:48:22.83083+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:27.72806+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.962929ms 2023-04-29T13:48:27.72814+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:27.82565+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.926614ms 2023-04-29T13:48:27.82571+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:30.2378+08:00 INFO [359133,1c47534f998a9e64] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=1c47534f998a9e64, body=] 2023-04-29T13:48:30.23877+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23881+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23883+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23886+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23887+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23889+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.2389+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23891+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23893+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23894+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23895+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23897+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23898+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23903+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23904+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23905+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23907+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23909+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.2391+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23912+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23913+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23914+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23918+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23919+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23921+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23922+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23923+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23925+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23926+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23927+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23929+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.2393+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23931+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23933+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23934+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23935+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23937+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23944+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23945+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23947+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23948+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23949+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23951+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23952+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23953+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23955+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23956+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23957+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23958+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.2396+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23962+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23963+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23964+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23966+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.2397+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23972+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23973+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23974+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23976+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23977+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23978+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.2398+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23981+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23982+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23984+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23985+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23986+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23987+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23989+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.2399+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23991+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23993+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23994+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23995+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.23998+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.23999+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24001+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24002+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24003+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24005+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24006+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24009+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.2401+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24012+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24013+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24015+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24016+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24017+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24019+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.2402+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24021+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24023+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24024+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24025+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24026+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24028+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24029+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24031+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24032+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24033+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24034+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24091+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24095+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24096+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24098+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24099+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.241+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24102+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24103+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24104+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24106+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24107+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24108+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.2411+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24111+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24112+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24114+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24115+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24117+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24118+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24121+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24122+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24123+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24125+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24126+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24127+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24129+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.2413+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24131+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24133+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24134+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24136+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:30.24137+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:30.24264+08:00 INFO [359133,84c5593b5530ebe6] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=84c5593b5530ebe6, body=] 2023-04-29T13:48:30.24277+08:00 INFO [359133,5b0b24756ccb26b3] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=5b0b24756ccb26b3, body=] 2023-04-29T13:48:30.24386+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:48:30.2439+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:48:32.72708+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.32712ms 2023-04-29T13:48:32.72716+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:32.82539+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.610309ms 2023-04-29T13:48:32.82549+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:37.73142+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.865485ms 2023-04-29T13:48:37.7315+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:37.82553+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.071016ms 2023-04-29T13:48:37.82559+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:42.72901+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.603138ms 2023-04-29T13:48:42.72908+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:42.82556+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.893913ms 2023-04-29T13:48:42.82562+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:45.23527+08:00 INFO [359133,430bd3e14f6e7be2] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=430bd3e14f6e7be2, body=] 2023-04-29T13:48:45.23547+08:00 INFO [359133,f83fb9b9eb79fb72] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=f83fb9b9eb79fb72, body=] 2023-04-29T13:48:45.23728+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:48:45.23733+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:48:45.23927+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.23931+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.23933+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.23935+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.23936+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.23939+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.23941+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.23942+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.23944+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.23945+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.23947+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.23948+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.23949+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.23954+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.23957+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.23958+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.23959+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.2396+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.23962+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.23963+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.23965+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.23966+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.23967+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.23969+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.2397+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.23971+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.23973+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.23974+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.23976+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.23978+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.2398+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.23981+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.23982+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.23984+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.23985+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.23986+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.23987+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.23989+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.2399+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.23991+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.23993+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.23994+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.23996+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.23997+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.23998+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.23999+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24001+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24002+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24003+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24005+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24006+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24007+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24009+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.2401+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24011+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24012+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24014+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24015+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24016+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24017+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24019+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.2402+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24021+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24022+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24027+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24029+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.2403+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24031+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24035+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24039+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24041+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24042+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24043+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24045+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24046+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24048+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24065+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24067+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24068+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.2407+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24071+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24072+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24073+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24075+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24076+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24077+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24078+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.2408+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24081+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24082+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24083+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24085+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24086+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24087+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24088+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.2409+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24091+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24092+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24093+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24095+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24096+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24097+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24145+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24149+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.2415+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24169+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24171+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24172+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24174+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24175+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24177+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24178+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24179+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24181+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24182+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24183+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24185+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24186+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24188+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24189+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.2419+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24192+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24193+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24194+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24195+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24197+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24198+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24199+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24201+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24202+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24203+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24204+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.24206+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:48:45.24207+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:48:45.25446+08:00 INFO [359133,8b06e9a34fd939bc] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=8b06e9a34fd939bc, body=] 2023-04-29T13:48:47.72759+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.177018ms 2023-04-29T13:48:47.72766+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:47.82528+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.700611ms 2023-04-29T13:48:47.8254+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:52.75236+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=22.199319ms 2023-04-29T13:48:52.75244+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:52.82974+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.134774ms 2023-04-29T13:48:52.82983+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:57.72692+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.940815ms 2023-04-29T13:48:57.72699+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:48:57.82575+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.427721ms 2023-04-29T13:48:57.82581+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:00.23533+08:00 INFO [359133,38154010d7b437ad] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=38154010d7b437ad, body=] 2023-04-29T13:49:00.2363+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23635+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23636+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23639+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23641+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23642+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23643+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23644+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23647+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23648+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.2365+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23651+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23652+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23653+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23655+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23657+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23659+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.2366+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23661+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23663+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23664+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23665+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23667+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23668+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23669+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.2367+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23672+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23673+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23674+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23676+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23677+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23678+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.2368+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23681+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23682+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23684+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23685+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23686+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23688+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23689+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23691+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23692+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23694+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23698+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23705+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23707+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23708+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23709+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23711+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23712+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23713+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23715+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23716+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23717+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23719+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.2372+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23723+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23724+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23725+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23727+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23728+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23734+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.2374+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23741+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23743+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23744+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23746+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23749+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23754+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23757+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23758+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23759+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23761+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23762+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23766+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23767+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23771+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23773+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23774+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23776+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23777+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23778+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.2378+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23781+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23783+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23784+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23785+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23786+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23844+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23848+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23852+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23853+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23855+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23857+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23858+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23859+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23861+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23862+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23863+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23865+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23866+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23867+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23869+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.2387+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23871+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23873+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23874+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23875+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23877+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23878+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23879+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23881+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23882+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23883+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23884+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23886+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.23887+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:00.23888+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:00.24017+08:00 INFO [359133,eaae6f5c2de7e4cc] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=eaae6f5c2de7e4cc, body=] 2023-04-29T13:49:00.2403+08:00 INFO [359133,cbf9fb545738e6c3] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=cbf9fb545738e6c3, body=] 2023-04-29T13:49:00.24152+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:49:00.24156+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:49:02.72671+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.545309ms 2023-04-29T13:49:02.72678+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:02.82503+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.692911ms 2023-04-29T13:49:02.82511+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:07.72713+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.537622ms 2023-04-29T13:49:07.72721+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:07.82768+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.870013ms 2023-04-29T13:49:07.82776+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:12.72663+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.862313ms 2023-04-29T13:49:12.72671+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:12.82488+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.522708ms 2023-04-29T13:49:12.82494+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:15.23652+08:00 INFO [359133,2ecfc0ca01b066b2] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=2ecfc0ca01b066b2, body=] 2023-04-29T13:49:15.23669+08:00 INFO [359133,c15a5e347550f745] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=c15a5e347550f745, body=] 2023-04-29T13:49:15.23784+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:49:15.23789+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:49:15.23903+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23909+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23921+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23923+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23925+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23926+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23927+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23929+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23932+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23934+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23935+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23937+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.2394+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23941+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23942+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23944+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23945+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23946+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23948+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23949+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23951+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23952+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23953+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23954+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23956+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23957+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23958+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.2396+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23961+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23963+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23965+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23966+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23967+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23969+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23971+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23972+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23973+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23975+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23977+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23978+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.2398+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23981+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23982+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23984+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23985+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23987+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23989+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.2399+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23991+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23993+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23994+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23995+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23997+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.23998+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.23999+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24001+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24002+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24003+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24004+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24006+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24007+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24008+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.2401+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24012+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24016+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24022+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24024+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24026+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24033+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24034+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.2404+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24043+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24051+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24053+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24054+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24056+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24057+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24058+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.2406+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24061+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24062+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24064+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24065+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24066+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24068+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24069+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24072+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24073+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24074+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24076+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24077+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24078+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.2408+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24081+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24082+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24084+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24085+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24086+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24088+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24089+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.2409+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24092+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24154+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24158+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.2416+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24161+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24163+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24164+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24165+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24167+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24168+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24169+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24171+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24173+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24174+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24175+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24177+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24178+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24179+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24181+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24182+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24183+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24184+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24186+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24187+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24188+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.2419+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24191+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24192+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24194+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24195+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24196+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.24197+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:15.24199+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:15.25292+08:00 INFO [359133,25e7f98f4efc138b] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=25e7f98f4efc138b, body=] 2023-04-29T13:49:17.72606+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.635309ms 2023-04-29T13:49:17.72612+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:17.82579+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.902514ms 2023-04-29T13:49:17.82586+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:22.72722+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.091717ms 2023-04-29T13:49:22.7273+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:22.82553+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.284619ms 2023-04-29T13:49:22.8256+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:27.73202+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.661982ms 2023-04-29T13:49:27.73208+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:27.82494+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.506008ms 2023-04-29T13:49:27.825+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:30.23493+08:00 INFO [359133,01733e4d0780e910] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=01733e4d0780e910, body=] 2023-04-29T13:49:30.23517+08:00 INFO [359133,abb4eada1d8dc503] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=abb4eada1d8dc503, body=] 2023-04-29T13:49:30.23601+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:49:30.23605+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:49:30.23696+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23701+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23707+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23708+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23711+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23712+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23714+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23715+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23718+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.2372+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23723+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23725+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23726+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23727+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23728+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.2373+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23732+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23733+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23735+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23736+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23739+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.2374+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23741+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23743+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23745+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23746+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23749+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.2375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23753+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23754+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23757+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23758+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23759+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23761+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23762+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23765+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23766+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23767+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23769+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.2377+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23771+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23773+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23774+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23775+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23776+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23778+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23779+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23781+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23782+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23784+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23785+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23786+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23789+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.2379+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23793+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23794+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23798+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23802+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23804+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23806+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23808+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23809+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23811+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23813+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23814+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23815+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23817+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23818+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23819+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23821+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23822+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23823+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23824+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23827+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23828+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23829+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23831+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23834+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23835+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23838+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.2384+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23842+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23843+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23907+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23911+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23913+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23914+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23916+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23919+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.2392+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23922+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23923+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23925+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23926+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23927+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23929+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.2393+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23931+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23932+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23934+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23935+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23936+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23939+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23941+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23942+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23944+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23945+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23946+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23948+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23953+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23955+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23957+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23958+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.23959+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:30.23961+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:30.25015+08:00 INFO [359133,5f0b4e5cbe6237f3] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=5f0b4e5cbe6237f3, body=] 2023-04-29T13:49:32.72761+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.741026ms 2023-04-29T13:49:32.72768+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:32.82516+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.747312ms 2023-04-29T13:49:32.82522+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:37.72705+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.753311ms 2023-04-29T13:49:37.72713+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:37.82498+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.542708ms 2023-04-29T13:49:37.82504+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:42.72704+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.616609ms 2023-04-29T13:49:42.72711+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:42.8255+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.64781ms 2023-04-29T13:49:42.82558+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:45.23507+08:00 INFO [359133,3a3af57336d9619b] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=3a3af57336d9619b, body=] 2023-04-29T13:49:45.2353+08:00 INFO [359133,332646f357b76aac] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=332646f357b76aac, body=] 2023-04-29T13:49:45.23634+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:49:45.2364+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:49:45.23744+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23749+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.2375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23752+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23753+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23754+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23756+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23757+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23758+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.2376+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23761+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23762+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23764+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23765+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23766+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23774+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23776+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23778+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23779+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.2378+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23782+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23783+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23784+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23786+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23787+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23789+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.2379+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23793+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23794+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23797+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23798+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23799+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23801+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23802+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23803+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23805+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23808+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23809+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.2381+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23812+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23814+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23815+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23817+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23818+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23819+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23821+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23822+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23823+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23826+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23828+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23831+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23832+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23833+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23835+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23836+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23841+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23843+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23846+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23849+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23851+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23854+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23855+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23856+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23858+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23859+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23861+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23862+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23863+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23865+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23866+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23867+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23869+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23875+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23877+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23878+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23879+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23881+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23882+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23883+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23885+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23886+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23888+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23891+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23894+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23895+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23896+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23898+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23899+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.239+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23902+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23904+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23905+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23906+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23908+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23911+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23912+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23914+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23916+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23917+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23918+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23968+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23976+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23978+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23979+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23981+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23982+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23984+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23985+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23986+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23987+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23989+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.2399+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23991+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23993+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23994+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23996+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23997+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.23998+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.23999+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.24001+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.24002+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.24003+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.24005+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.24006+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.24008+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.24009+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.2401+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.24012+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.24013+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.24014+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.24016+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:49:45.24017+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:49:45.25056+08:00 INFO [359133,8e91657d39b4b224] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=8e91657d39b4b224, body=] 2023-04-29T13:49:47.72658+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.753611ms 2023-04-29T13:49:47.72664+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:47.82509+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.735111ms 2023-04-29T13:49:47.82519+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:52.73889+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.811712ms 2023-04-29T13:49:52.73903+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:52.82652+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.650525ms 2023-04-29T13:49:52.82659+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:57.7269+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.980614ms 2023-04-29T13:49:57.72697+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:49:57.82614+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.995529ms 2023-04-29T13:49:57.82622+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:50:00.23486+08:00 INFO [359133,efc1416d003d59dd] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/host, client=10.0.10.102, ocpServerIp=, traceId=efc1416d003d59dd, body=] 2023-04-29T13:50:00.23506+08:00 INFO [359133,c30f6795e73d58ea] caller=common/middleware.go:59:func1: API request: [GET /metrics/ob/basic, client=10.0.10.102, ocpServerIp=, traceId=c30f6795e73d58ea, body=] 2023-04-29T13:50:00.236+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23604+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23606+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23607+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23609+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.2361+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23612+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23613+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23614+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23616+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23617+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23618+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.2362+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23621+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23622+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23623+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23625+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23626+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23628+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23629+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.2363+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23632+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23633+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23635+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23636+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.2364+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23643+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23644+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23645+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23647+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23648+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23649+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23651+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23652+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23653+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23655+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23656+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23657+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23658+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.2366+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23661+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23662+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23665+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23667+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23675+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23683+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23686+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23688+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.2369+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23691+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23692+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23694+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23695+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23696+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23698+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.237+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23703+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23706+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.2371+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23712+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23715+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23717+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23719+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23721+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23722+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23731+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23733+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23739+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.2374+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23742+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23743+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23744+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23747+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23748+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.2375+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23751+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23752+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23754+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23755+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23758+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23759+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23762+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23763+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23764+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23776+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23778+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23782+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23784+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23785+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23786+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23788+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.2379+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23791+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23792+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23794+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23795+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23796+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23798+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23799+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.238+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23805+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23807+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23859+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23863+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23864+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23866+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23868+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23869+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23875+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23876+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23879+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23882+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23883+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23885+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23886+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23887+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23889+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.2389+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23892+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23895+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23897+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23898+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23899+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.239+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23902+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23904+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23905+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23907+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23908+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.2391+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23912+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23913+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.23914+08:00 WARN [359133,] caller=label/mount_label.go:160:Process: can not found PV of dataMountPath 2023-04-29T13:50:00.23915+08:00 WARN [359133,] caller=label/mount_label.go:168:Process: can not found PV of logMountPath 2023-04-29T13:50:00.24021+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:50:00.24025+08:00 WARN [359133,] caller=runtime/asm_amd64.s:1581:goexit: condition not satisfied, skip do collect for:ob_table 2023-04-29T13:50:00.25124+08:00 INFO [359133,05c82a8d57c22673] caller=common/middleware.go:59:func1: API request: [GET /metrics/node/ob, client=10.0.10.102, ocpServerIp=, traceId=05c82a8d57c22673, body=] 2023-04-29T13:50:02.72643+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.379106ms 2023-04-29T13:50:02.72649+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:50:02.82564+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.512323ms 2023-04-29T13:50:02.8257+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:50:07.72956+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.503308ms 2023-04-29T13:50:07.72965+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:50:07.82597+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.968415ms 2023-04-29T13:50:07.82608+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:50:12.73149+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.333877ms 2023-04-29T13:50:12.73156+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-04-29T13:50:12.82695+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.119331ms 2023-04-29T13:50:12.82707+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:51:54.12976+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.163846ms 2023-05-18T10:51:54.12985+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:51:54.22924+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.035273ms 2023-05-18T10:51:54.22933+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:51:59.12917+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.858627ms 2023-05-18T10:51:59.12926+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:51:59.24749+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=30.192232ms 2023-05-18T10:51:59.2476+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:04.12857+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.335933ms 2023-05-18T10:52:04.12868+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:04.22551+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.334419ms 2023-05-18T10:52:04.22561+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:09.12827+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.468536ms 2023-05-18T10:52:09.12838+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:09.22734+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.389834ms 2023-05-18T10:52:09.22745+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:14.12909+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.77754ms 2023-05-18T10:52:14.12921+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:14.22706+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.986328ms 2023-05-18T10:52:14.22716+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:19.12847+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.975729ms 2023-05-18T10:52:19.12856+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:19.22718+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.04743ms 2023-05-18T10:52:19.2273+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:24.13284+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.169931ms 2023-05-18T10:52:24.13293+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:24.2266+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.09493ms 2023-05-18T10:52:24.22668+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:29.15992+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=38.40695ms 2023-05-18T10:52:29.16003+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:29.23967+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.259047ms 2023-05-18T10:52:29.23982+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:34.12674+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.017915ms 2023-05-18T10:52:34.12681+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:34.22491+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.908899ms 2023-05-18T10:52:34.22499+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:39.12703+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.752211ms 2023-05-18T10:52:39.1271+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:39.2254+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.322405ms 2023-05-18T10:52:39.22549+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:43.34566+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 14.170956061s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T10:52:43.34576+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:52:43.34579+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:52:43.34587+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 14.159992904s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T10:52:43.3459+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:52:43.34591+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:52:43.34708+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_server, duration: 14.172341681s (over 100ms), sql: select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status 2023-05-18T10:52:43.34712+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:52:43.34715+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_server, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:52:43.3472+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:52:43.34767+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_unit_config, duration: 14.118842116s (over 100ms), sql: select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ? 2023-05-18T10:52:43.34772+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ?, args:[10.0.10.102], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:52:43.34775+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_unit_config, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:52:43.34786+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_assigned, duration: 14.162451739s (over 100ms), sql: select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ? 2023-05-18T10:52:43.34789+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:52:43.34791+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_assigned, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:52:43.348+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 44.167819162s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:52:43.34802+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:52:43.34803+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:52:43.34815+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 44.168043165s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:52:43.34819+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:52:43.34822+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:52:43.34843+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_disk, duration: 14.119524025s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T10:52:43.34847+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:52:43.34849+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_disk, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:52:43.34863+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_resource, duration: 14.119762628s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T10:52:43.34866+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:52:43.34868+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_resource, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:52:44.12717+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.229718ms 2023-05-18T10:52:44.12726+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:44.2261+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.077816ms 2023-05-18T10:52:44.22617+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:49.12713+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.827412ms 2023-05-18T10:52:49.1272+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:49.22494+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.754711ms 2023-05-18T10:52:49.22503+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:53.26403+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.915753077s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:52:53.26411+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:52:53.26413+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:52:53.26425+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.916165482s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:52:53.2643+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:52:53.26434+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:52:53.40468+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:52:54.12721+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.960514ms 2023-05-18T10:52:54.12728+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:54.22479+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.282304ms 2023-05-18T10:52:54.22486+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:59.12694+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.68791ms 2023-05-18T10:52:59.12702+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:52:59.2259+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.732511ms 2023-05-18T10:52:59.22597+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:03.2017+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.937494488s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:53:03.20177+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:03.20181+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:03.21156+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.947184226s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:53:03.21162+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:03.21164+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:03.41243+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:53:04.12693+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.593009ms 2023-05-18T10:53:04.12701+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:04.22476+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.602809ms 2023-05-18T10:53:04.22483+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:09.12597+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.383405ms 2023-05-18T10:53:09.12606+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:09.22553+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.484907ms 2023-05-18T10:53:09.22561+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:13.11045+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.908562874s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:53:13.11052+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:13.11054+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:13.20141+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.989725435s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:53:13.20147+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:13.2015+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:13.49914+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:53:14.12681+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.595809ms 2023-05-18T10:53:14.1269+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:14.22516+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.568808ms 2023-05-18T10:53:14.22523+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:19.12625+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.659409ms 2023-05-18T10:53:19.12633+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:19.22431+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.174302ms 2023-05-18T10:53:19.22439+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:23.51683+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields: error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:53:24.08455+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.908484972s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:53:24.08463+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:24.08466+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:24.09433+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.918355014s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:53:24.09437+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:24.0944+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:24.12643+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.66281ms 2023-05-18T10:53:24.12649+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:24.22462+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.334905ms 2023-05-18T10:53:24.22469+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:29.13887+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.66501ms 2023-05-18T10:53:29.13894+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:29.2259+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.541122ms 2023-05-18T10:53:29.22599+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:33.61701+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:53:34.1269+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.914614ms 2023-05-18T10:53:34.12698+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:34.22547+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.606309ms 2023-05-18T10:53:34.22555+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:39.1268+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.762111ms 2023-05-18T10:53:39.12687+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:39.12941+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.943603375s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:53:39.12945+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.12947+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.12985+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.943572875s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:53:39.12988+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.1299+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.1416+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_disk, duration: 9.931525502s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T10:53:39.14164+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.14167+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_disk, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.14232+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_resource, duration: 9.931082196s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T10:53:39.14235+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.14237+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_resource, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.17922+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:203:collectDBData: slow sql, duration: 9.991839465s (over 100ms), sql: SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META' 2023-05-18T10:53:39.17928+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:206:collectDBData: failed to do collect with sql SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META', args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.1793+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key jointable-3, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.17939+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:203:collectDBData: slow sql, duration: 9.966702106s (over 100ms), sql: SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META' 2023-05-18T10:53:39.17941+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:206:collectDBData: failed to do collect with sql SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META', args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.17942+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key jointable-3, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.17945+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:203:collectDBData: slow sql, duration: 9.992373073s (over 100ms), sql: SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META' 2023-05-18T10:53:39.17946+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:206:collectDBData: failed to do collect with sql SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META', args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.17947+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key jointable-1, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.17949+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:203:collectDBData: slow sql, duration: 9.969282642s (over 100ms), sql: SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META' 2023-05-18T10:53:39.17951+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:206:collectDBData: failed to do collect with sql SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META', args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.17952+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key jointable-1, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.18946+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_assigned, duration: 10.003836337s (over 100ms), sql: select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ? 2023-05-18T10:53:39.18951+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.18953+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_assigned, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.22474+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_server, duration: 10.057763508s (over 100ms), sql: select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status 2023-05-18T10:53:39.22479+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.22481+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_server, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.22489+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.428307ms 2023-05-18T10:53:39.22492+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:39.29127+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 10.10400217s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T10:53:39.29132+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.29134+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.29141+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 10.124217059s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T10:53:39.29144+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.29145+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.32078+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_unit_config, duration: 10.10960135s (over 100ms), sql: select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ? 2023-05-18T10:53:39.32083+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ?, args:[10.0.10.102], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:39.32084+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_unit_config, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:43.72418+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:53:44.12671+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.774711ms 2023-05-18T10:53:44.12679+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:44.22584+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.785011ms 2023-05-18T10:53:44.22591+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:49.12661+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.742711ms 2023-05-18T10:53:49.12669+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:49.22533+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.140402ms 2023-05-18T10:53:49.22539+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:53.75283+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields: error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:53:54.07764+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.901718376s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:53:54.0777+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:54.07772+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:54.10771+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.931714805s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:53:54.10777+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:54.10779+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:53:54.127+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.844112ms 2023-05-18T10:53:54.12706+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:54.22463+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.243304ms 2023-05-18T10:53:54.22469+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:59.1265+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.862812ms 2023-05-18T10:53:59.12657+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:53:59.2252+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.422306ms 2023-05-18T10:53:59.22527+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:04.1269+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.618609ms 2023-05-18T10:54:04.12697+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:04.22496+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.365305ms 2023-05-18T10:54:04.22506+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:09.12732+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.500521ms 2023-05-18T10:54:09.12746+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:09.12817+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.951819993s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:54:09.12821+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:09.12825+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:09.12839+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.951980895s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:54:09.12841+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:09.12843+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:09.22502+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.552908ms 2023-05-18T10:54:09.22511+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:09.22517+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields: error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:54:09.25943+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_index, duration: 1m39.995008249s (over 100ms), sql: select /*+ MONITOR_AGENT QUERY_TIMEOUT(100000000) */ count(*) as cnt from CDB_INDEXES where status in ('ERROR','UNUSABLE') 2023-05-18T10:54:09.25947+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /*+ MONITOR_AGENT QUERY_TIMEOUT(100000000) */ count(*) as cnt from CDB_INDEXES where status in ('ERROR','UNUSABLE'), args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 100000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:09.25951+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_index, err: Error 4012: Timeout, query has reached the maximum query timeout: 100000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:14.12706+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.945714ms 2023-05-18T10:54:14.12714+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:14.22591+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.934114ms 2023-05-18T10:54:14.22599+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:19.12692+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.505007ms 2023-05-18T10:54:19.12699+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:19.22461+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.198203ms 2023-05-18T10:54:19.22468+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:19.31689+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:54:24.08663+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.9104585s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:54:24.08671+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:24.08673+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:24.08681+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.910569802s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:54:24.08683+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:24.08684+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:24.12675+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.544208ms 2023-05-18T10:54:24.12682+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:24.22425+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.112402ms 2023-05-18T10:54:24.22433+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:29.14235+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=20.9747ms 2023-05-18T10:54:29.14242+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:29.22617+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.699524ms 2023-05-18T10:54:29.22629+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:34.12706+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.157916ms 2023-05-18T10:54:34.12715+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:34.22538+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.70181ms 2023-05-18T10:54:34.22545+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:39.12726+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.835612ms 2023-05-18T10:54:39.12734+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:39.12743+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_assigned, duration: 9.934701747s (over 100ms), sql: select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ? 2023-05-18T10:54:39.12747+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:39.12749+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_assigned, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:39.16698+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.987406302s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:54:39.16703+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:39.16704+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:39.16711+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.987474103s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:54:39.16713+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:39.16714+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:39.21717+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:54:39.22502+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.69011ms 2023-05-18T10:54:39.22509+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:39.22653+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_resource, duration: 10.015288801s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T10:54:39.22657+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:39.22661+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_resource, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:39.22735+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_server, duration: 10.047820266s (over 100ms), sql: select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status 2023-05-18T10:54:39.22746+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:39.22749+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_server, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:39.23662+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_disk, duration: 10.026643664s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T10:54:39.23665+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:39.23666+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_disk, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:39.2382+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_unit_config, duration: 10.027011868s (over 100ms), sql: select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ? 2023-05-18T10:54:39.23824+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ?, args:[10.0.10.102], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:39.23826+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_unit_config, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:39.24737+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 10.054331559s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T10:54:39.24741+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:39.24743+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:39.25742+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 10.078002998s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T10:54:39.25747+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:39.2575+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:44.12684+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.569208ms 2023-05-18T10:54:44.12692+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:44.22561+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.499407ms 2023-05-18T10:54:44.22568+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:49.12699+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.67921ms 2023-05-18T10:54:49.12708+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:49.22477+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.156002ms 2023-05-18T10:54:49.22484+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:49.28852+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:54:54.10124+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.925164812s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:54:54.10131+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:54.10135+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:54.10155+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.925557817s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:54:54.1016+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:54.10163+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:54:54.1265+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.521707ms 2023-05-18T10:54:54.12659+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:54.22552+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.631709ms 2023-05-18T10:54:54.22561+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:59.12613+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.943699ms 2023-05-18T10:54:59.12619+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:54:59.22496+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.430706ms 2023-05-18T10:54:59.22503+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:04.12557+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.862798ms 2023-05-18T10:55:04.12565+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:04.22486+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.676396ms 2023-05-18T10:55:04.22494+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:09.0786+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.902647889s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:55:09.07866+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:09.07867+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:09.07873+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.90272879s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:55:09.07877+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:09.07878+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:09.12618+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.879899ms 2023-05-18T10:55:09.12624+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:09.15803+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:55:09.22482+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.832298ms 2023-05-18T10:55:09.22488+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:14.12644+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.0064ms 2023-05-18T10:55:14.12651+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:14.22459+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.263304ms 2023-05-18T10:55:14.22466+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:19.12612+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.627195ms 2023-05-18T10:55:19.12618+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:19.21392+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:55:19.22466+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.522393ms 2023-05-18T10:55:19.22472+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:24.10802+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.931619804s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:55:24.10808+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:24.1081+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:24.11783+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.941488444s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:55:24.11787+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:24.11788+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:24.1256+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.596895ms 2023-05-18T10:55:24.12566+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:24.22475+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.788397ms 2023-05-18T10:55:24.22482+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:29.13761+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.764997ms 2023-05-18T10:55:29.13767+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:29.22476+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.132302ms 2023-05-18T10:55:29.22483+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:34.12639+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.930099ms 2023-05-18T10:55:34.12647+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:34.22477+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.806898ms 2023-05-18T10:55:34.22485+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:39.12601+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.713196ms 2023-05-18T10:55:39.12608+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:39.14224+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_resource, duration: 9.931296999s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T10:55:39.1423+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:39.14232+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_resource, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:39.14268+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_disk, duration: 9.931696405s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T10:55:39.14271+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:39.14272+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_disk, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:39.15255+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_assigned, duration: 9.966159297s (over 100ms), sql: select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ? 2023-05-18T10:55:39.15261+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:39.15263+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_assigned, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:39.20204+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 10.014704792s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:55:39.20208+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:39.2021+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:39.20216+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 10.015160099s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:55:39.20218+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:39.2022+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:39.22424+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.741596ms 2023-05-18T10:55:39.22429+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:39.28368+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:55:39.28382+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 10.097104172s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T10:55:39.28386+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:39.28388+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:39.28394+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_server, duration: 10.097104571s (over 100ms), sql: select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status 2023-05-18T10:55:39.28396+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:39.28397+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_server, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:39.28402+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 10.09627016s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T10:55:39.28405+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:39.28406+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:39.30308+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_unit_config, duration: 10.092222001s (over 100ms), sql: select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ? 2023-05-18T10:55:39.30312+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ?, args:[10.0.10.102], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:39.30314+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_unit_config, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:44.12622+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.833698ms 2023-05-18T10:55:44.1263+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:44.22491+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.928299ms 2023-05-18T10:55:44.22497+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:49.12544+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.629695ms 2023-05-18T10:55:49.1255+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:49.175+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_index, duration: 1m39.915452159s (over 100ms), sql: select /*+ MONITOR_AGENT QUERY_TIMEOUT(100000000) */ count(*) as cnt from CDB_INDEXES where status in ('ERROR','UNUSABLE') 2023-05-18T10:55:49.17507+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /*+ MONITOR_AGENT QUERY_TIMEOUT(100000000) */ count(*) as cnt from CDB_INDEXES where status in ('ERROR','UNUSABLE'), args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 100000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:49.17509+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_index, err: Error 4012: Timeout, query has reached the maximum query timeout: 100000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:49.22486+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.391905ms 2023-05-18T10:55:49.22493+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:49.36686+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:55:54.08652+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.909879992s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:55:54.08659+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:54.08662+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:54.08669+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.910004494s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:55:54.08671+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:54.08672+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:55:54.12619+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.968899ms 2023-05-18T10:55:54.12624+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:54.22429+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.648295ms 2023-05-18T10:55:54.22435+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:59.12613+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.858598ms 2023-05-18T10:55:59.1262+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:55:59.22406+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.689396ms 2023-05-18T10:55:59.22412+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:04.12608+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.807997ms 2023-05-18T10:56:04.12614+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:04.22424+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.595194ms 2023-05-18T10:56:04.2243+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:09.08123+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.904946222s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:56:09.08129+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:09.08131+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:09.09109+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.914731462s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:56:09.09114+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:09.09117+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:09.12529+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.643895ms 2023-05-18T10:56:09.12535+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:09.16052+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:56:09.22423+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.720896ms 2023-05-18T10:56:09.22428+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:14.12641+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.313705ms 2023-05-18T10:56:14.12647+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:14.22435+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.725796ms 2023-05-18T10:56:14.22441+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:19.1265+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.906756ms 2023-05-18T10:56:19.12657+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:19.22431+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.224121ms 2023-05-18T10:56:19.22436+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:19.26503+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:56:24.07821+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.902240783s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:56:24.07826+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:24.07828+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:24.07837+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.902489894s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:56:24.0784+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:24.07842+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:24.12632+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.707445ms 2023-05-18T10:56:24.1264+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:24.22449+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.543037ms 2023-05-18T10:56:24.22455+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:29.1429+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=21.680317ms 2023-05-18T10:56:29.14296+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:29.22422+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.101466ms 2023-05-18T10:56:29.2243+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:34.12645+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.218572ms 2023-05-18T10:56:34.12652+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:34.22459+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.619841ms 2023-05-18T10:56:34.22466+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:39.10127+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:203:collectDBData: slow sql, duration: 9.907434315s (over 100ms), sql: SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META' 2023-05-18T10:56:39.10132+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:206:collectDBData: failed to do collect with sql SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META', args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.10134+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key jointable-1, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.10137+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:203:collectDBData: slow sql, duration: 9.907400013s (over 100ms), sql: SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META' 2023-05-18T10:56:39.10138+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:206:collectDBData: failed to do collect with sql SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META', args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.10139+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key jointable-3, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.11409+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:203:collectDBData: slow sql, duration: 9.901848227s (over 100ms), sql: SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META' 2023-05-18T10:56:39.11412+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:206:collectDBData: failed to do collect with sql SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META', args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.11413+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key jointable-3, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.11416+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:203:collectDBData: slow sql, duration: 9.902136942s (over 100ms), sql: SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META' 2023-05-18T10:56:39.11417+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:206:collectDBData: failed to do collect with sql SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META', args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.11418+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key jointable-1, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.12635+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.00036ms 2023-05-18T10:56:39.12642+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:39.14169+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_disk, duration: 9.931717766s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T10:56:39.14175+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.14183+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_disk, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.14193+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_resource, duration: 9.932016581s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T10:56:39.14195+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.14197+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_resource, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.1521+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.975422017s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:56:39.15214+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.15215+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.16226+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_assigned, duration: 9.968219946s (over 100ms), sql: select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ? 2023-05-18T10:56:39.16231+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.16233+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_assigned, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.17214+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.995102332s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:56:39.17219+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.17222+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.22431+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.700945ms 2023-05-18T10:56:39.22437+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:39.23248+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:56:39.23262+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_server, duration: 10.055631749s (over 100ms), sql: select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status 2023-05-18T10:56:39.23265+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.23267+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_server, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.23274+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 10.055804359s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T10:56:39.23277+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.23279+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.23288+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 10.038947691s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T10:56:39.2329+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.23291+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.31278+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_unit_config, duration: 10.100235748s (over 100ms), sql: select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ? 2023-05-18T10:56:39.31284+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ?, args:[10.0.10.102], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:39.31286+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_unit_config, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:44.12641+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.918657ms 2023-05-18T10:56:44.12647+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:44.22437+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.818851ms 2023-05-18T10:56:44.22445+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:49.12623+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.950858ms 2023-05-18T10:56:49.1263+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:49.22431+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.684544ms 2023-05-18T10:56:49.22438+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:49.23888+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:56:54.12634+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.119667ms 2023-05-18T10:56:54.12642+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:54.17382+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.997396549s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:56:54.17387+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:54.17389+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:54.17395+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.997479554s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:56:54.17397+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:54.17399+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:56:54.22404+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.537937ms 2023-05-18T10:56:54.2241+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:59.12566+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.722146ms 2023-05-18T10:56:59.12572+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:56:59.22572+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.554889ms 2023-05-18T10:56:59.22578+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:04.12573+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.777349ms 2023-05-18T10:57:04.12579+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:04.22405+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.554738ms 2023-05-18T10:57:04.22412+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:09.08085+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.904467562s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:57:09.08091+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:09.08095+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:09.08101+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.904574467s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:57:09.08104+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:09.08105+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:09.12607+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.654343ms 2023-05-18T10:57:09.12613+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:09.20172+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields: error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:57:09.22436+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.817952ms 2023-05-18T10:57:09.22442+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:14.12554+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.835552ms 2023-05-18T10:57:14.12561+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:14.22389+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.676544ms 2023-05-18T10:57:14.22396+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:19.12563+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.880454ms 2023-05-18T10:57:19.12569+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:19.20314+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:57:19.22427+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.801851ms 2023-05-18T10:57:19.22434+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:24.11763+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.940918298s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:57:24.11769+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:24.11771+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:24.11779+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.94221586s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:57:24.11782+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:24.11783+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:24.12574+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.793835ms 2023-05-18T10:57:24.12579+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:24.22411+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.656133ms 2023-05-18T10:57:24.22417+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:29.1273+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.879937ms 2023-05-18T10:57:29.12737+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:29.14296+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_index, duration: 1m39.967828888s (over 100ms), sql: select /*+ MONITOR_AGENT QUERY_TIMEOUT(100000000) */ count(*) as cnt from CDB_INDEXES where status in ('ERROR','UNUSABLE') 2023-05-18T10:57:29.14303+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /*+ MONITOR_AGENT QUERY_TIMEOUT(100000000) */ count(*) as cnt from CDB_INDEXES where status in ('ERROR','UNUSABLE'), args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 100000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:29.14305+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_index, err: Error 4012: Timeout, query has reached the maximum query timeout: 100000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:29.22423+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.782935ms 2023-05-18T10:57:29.22431+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:34.12627+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.049441ms 2023-05-18T10:57:34.12635+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:34.22452+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.578332ms 2023-05-18T10:57:34.22459+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:39.11238+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_assigned, duration: 9.927252629s (over 100ms), sql: select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ? 2023-05-18T10:57:39.11244+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:39.11246+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_assigned, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:39.12539+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.790135ms 2023-05-18T10:57:39.12545+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:39.12549+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.940297188s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:57:39.12552+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:39.12553+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:39.12562+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.940451492s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:57:39.12565+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:39.12568+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:39.14173+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_disk, duration: 9.9308479s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T10:57:39.14179+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:39.14182+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_disk, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:39.1419+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_resource, duration: 9.931071404s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T10:57:39.14193+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:39.14194+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_resource, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:39.1924+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_server, duration: 10.020153981s (over 100ms), sql: select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status 2023-05-18T10:57:39.19245+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:39.19248+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_server, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:39.19255+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 10.00710952s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T10:57:39.19257+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:39.19261+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:39.19264+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:57:39.19275+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 10.020288083s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T10:57:39.19277+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:39.19278+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:39.2141+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_unit_config, duration: 10.003325245s (over 100ms), sql: select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ? 2023-05-18T10:57:39.21415+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ?, args:[10.0.10.102], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:39.21418+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_unit_config, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:39.22407+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.696334ms 2023-05-18T10:57:39.22413+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:44.12596+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.901237ms 2023-05-18T10:57:44.12604+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:44.22449+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.702734ms 2023-05-18T10:57:44.22455+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:49.12598+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.834536ms 2023-05-18T10:57:49.12605+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:49.22449+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.656233ms 2023-05-18T10:57:49.22455+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:49.28027+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:57:54.12563+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.842136ms 2023-05-18T10:57:54.12569+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:54.15236+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.975407288s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:57:54.15242+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:54.15244+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:54.15251+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.976763615s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:57:54.15253+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:54.15255+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:57:54.22468+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.782935ms 2023-05-18T10:57:54.22473+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:59.12588+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.685433ms 2023-05-18T10:57:59.12595+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:57:59.2243+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.743434ms 2023-05-18T10:57:59.22437+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:04.12603+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.705433ms 2023-05-18T10:58:04.12609+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:04.22467+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.49673ms 2023-05-18T10:58:04.22473+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:09.12555+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.772135ms 2023-05-18T10:58:09.12562+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:09.15801+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.982031821s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:58:09.15806+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:09.15808+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:09.15815+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.982226225s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:58:09.15817+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:09.15818+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:09.20778+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:58:09.22396+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.461729ms 2023-05-18T10:58:09.22401+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:14.12625+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.948538ms 2023-05-18T10:58:14.12631+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:14.22438+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.710734ms 2023-05-18T10:58:14.22444+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:19.12641+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.923938ms 2023-05-18T10:58:19.12649+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:19.21787+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:58:19.22421+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.833836ms 2023-05-18T10:58:19.22427+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:24.12572+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.714134ms 2023-05-18T10:58:24.12579+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:24.1621+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.985317386s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:58:24.16216+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:24.16218+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:24.16224+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.986611712s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:58:24.16226+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:24.16228+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:24.2247+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.686533ms 2023-05-18T10:58:24.22476+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:29.14785+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.419684ms 2023-05-18T10:58:29.14792+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:29.22488+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.991211ms 2023-05-18T10:58:29.22495+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:34.12672+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.32202ms 2023-05-18T10:58:34.12679+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:34.2246+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.773804ms 2023-05-18T10:58:34.22466+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:39.09544+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.909474861s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:58:39.09552+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:39.09556+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:39.09561+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.909682867s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:58:39.09563+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:39.09565+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:39.12604+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.004511ms 2023-05-18T10:58:39.1261+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:39.14145+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_disk, duration: 9.930589696s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T10:58:39.1415+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:39.14152+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_disk, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:39.15509+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_resource, duration: 9.944265307s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T10:58:39.15514+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:39.15517+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_resource, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:39.1866+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_assigned, duration: 10.000843509s (over 100ms), sql: select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ? 2023-05-18T10:58:39.18664+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:39.18666+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_assigned, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:39.22443+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.131315ms 2023-05-18T10:58:39.2245+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:39.23657+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields: error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:58:39.24644+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 10.060291996s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T10:58:39.24649+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:39.24651+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:39.2466+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_server, duration: 10.073799002s (over 100ms), sql: select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status 2023-05-18T10:58:39.24662+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:39.24663+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_server, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:39.25651+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 10.083795502s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T10:58:39.25656+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:39.25659+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:39.29638+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_unit_config, duration: 10.085647758s (over 100ms), sql: select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ? 2023-05-18T10:58:39.29644+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ?, args:[10.0.10.102], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:39.29647+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_unit_config, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:44.12594+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.860806ms 2023-05-18T10:58:44.126+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:44.22523+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.144614ms 2023-05-18T10:58:44.22546+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:49.12585+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.798405ms 2023-05-18T10:58:49.12593+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:49.22448+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.530996ms 2023-05-18T10:58:49.22454+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:49.30941+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:58:54.12776+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.680161ms 2023-05-18T10:58:54.12783+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:54.17616+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.999878979s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:58:54.17622+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:54.17624+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:54.17633+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.999988082s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:58:54.17635+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:54.17637+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:58:54.2247+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.714302ms 2023-05-18T10:58:54.22476+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:59.12572+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.773004ms 2023-05-18T10:58:59.12578+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:58:59.22409+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.831905ms 2023-05-18T10:58:59.22415+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:04.12578+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.870607ms 2023-05-18T10:59:04.12585+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:04.22423+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.6344ms 2023-05-18T10:59:04.2243+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:09.06889+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_index, duration: 1m39.925797827s (over 100ms), sql: select /*+ MONITOR_AGENT QUERY_TIMEOUT(100000000) */ count(*) as cnt from CDB_INDEXES where status in ('ERROR','UNUSABLE') 2023-05-18T10:59:09.06895+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /*+ MONITOR_AGENT QUERY_TIMEOUT(100000000) */ count(*) as cnt from CDB_INDEXES where status in ('ERROR','UNUSABLE'), args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 100000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:09.06897+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_index, err: Error 4012: Timeout, query has reached the maximum query timeout: 100000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:09.12647+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.864107ms 2023-05-18T10:59:09.12653+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:09.17026+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.993742595s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:59:09.17033+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:09.17035+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:09.17042+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.993988102s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:59:09.17046+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:09.17047+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:09.22472+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.720502ms 2023-05-18T10:59:09.22478+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:09.23052+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:59:14.12598+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.136415ms 2023-05-18T10:59:14.12605+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:14.22494+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.815505ms 2023-05-18T10:59:14.22501+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:19.12582+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.836006ms 2023-05-18T10:59:19.12588+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:19.22451+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.929609ms 2023-05-18T10:59:19.22458+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:19.2534+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields: error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:59:24.12566+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.793905ms 2023-05-18T10:59:24.12573+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:24.13878+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.96200004s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:59:24.13883+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:24.13885+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:24.14789+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.972267049s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:59:24.14793+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:24.14797+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:24.22439+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.762203ms 2023-05-18T10:59:24.22447+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:29.16071+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=30.458916ms 2023-05-18T10:59:29.16077+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:29.2252+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.815735ms 2023-05-18T10:59:29.22526+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:34.12651+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.873755ms 2023-05-18T10:59:34.12658+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:34.22392+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.643647ms 2023-05-18T10:59:34.224+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:39.08991+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.908793854s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:59:39.08997+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.08999+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.09988+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.918812226s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:59:39.09992+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.09994+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.12604+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.72425ms 2023-05-18T10:59:39.12609+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:39.14077+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_resource, duration: 9.930859378s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T10:59:39.14081+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.14083+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_resource, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.14089+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_disk, duration: 9.930925381s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T10:59:39.14091+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.14093+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_disk, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.1503+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:203:collectDBData: slow sql, duration: 9.94030463s (over 100ms), sql: SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META' 2023-05-18T10:59:39.15034+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:206:collectDBData: failed to do collect with sql SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META', args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.15036+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key jointable-1, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.15044+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_assigned, duration: 9.965765997s (over 100ms), sql: select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ? 2023-05-18T10:59:39.15048+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.1505+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_assigned, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.15053+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:203:collectDBData: slow sql, duration: 9.938361573s (over 100ms), sql: SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META' 2023-05-18T10:59:39.15054+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:206:collectDBData: failed to do collect with sql SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META', args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.15056+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key jointable-3, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.18347+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:203:collectDBData: slow sql, duration: 9.998610019s (over 100ms), sql: SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META' 2023-05-18T10:59:39.18353+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:206:collectDBData: failed to do collect with sql SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META', args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.18355+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key jointable-1, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.18359+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:203:collectDBData: slow sql, duration: 9.999068533s (over 100ms), sql: SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META' 2023-05-18T10:59:39.18361+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:206:collectDBData: failed to do collect with sql SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META', args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.18362+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key jointable-3, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.22409+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.956359ms 2023-05-18T10:59:39.22415+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:39.25155+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 10.070624168s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T10:59:39.25162+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.25164+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.2517+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_server, duration: 10.070691671s (over 100ms), sql: select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status 2023-05-18T10:59:39.25173+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.25174+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_server, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.2518+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 10.066881756s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T10:59:39.25182+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.25184+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.25187+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields: error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:59:39.3113+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_unit_config, duration: 10.101479119s (over 100ms), sql: select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ? 2023-05-18T10:59:39.31134+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ?, args:[10.0.10.102], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:39.31136+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_unit_config, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:44.12619+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.689649ms 2023-05-18T10:59:44.12625+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:44.22434+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.648847ms 2023-05-18T10:59:44.2244+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:49.12543+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.687748ms 2023-05-18T10:59:49.12549+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:49.22499+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.850954ms 2023-05-18T10:59:49.22505+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:49.36454+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T10:59:54.12588+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.888656ms 2023-05-18T10:59:54.12594+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:54.13856+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.962132239s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:59:54.13863+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:54.13866+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:54.14812+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.971755097s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T10:59:54.14817+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:54.14819+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T10:59:54.22557+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.777389ms 2023-05-18T10:59:54.22565+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:59.12599+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.775152ms 2023-05-18T10:59:59.12605+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T10:59:59.22497+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.98466ms 2023-05-18T10:59:59.22503+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:04.12606+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.564244ms 2023-05-18T11:00:04.12612+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:04.22454+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.903057ms 2023-05-18T11:00:04.22461+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:09.12587+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.776952ms 2023-05-18T11:00:09.12593+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:09.17161+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.995451777s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:00:09.17166+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:09.17168+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:09.17175+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.995520079s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:00:09.17177+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:09.17179+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:09.21211+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T11:00:09.22954+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.592231ms 2023-05-18T11:00:09.22962+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:14.126+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.745351ms 2023-05-18T11:00:14.12605+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:14.22484+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.868555ms 2023-05-18T11:00:14.2249+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:19.12634+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.869356ms 2023-05-18T11:00:19.12641+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:19.22485+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.938457ms 2023-05-18T11:00:19.2249+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:19.22497+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T11:00:24.12569+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.687348ms 2023-05-18T11:00:24.12576+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:24.16388+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.987811993s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:00:24.16394+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:24.16396+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:24.16403+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.988036501s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:00:24.16406+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:24.16408+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:24.22457+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.937158ms 2023-05-18T11:00:24.22464+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:29.1722+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=26.878299ms 2023-05-18T11:00:29.17226+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:29.22451+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.018061ms 2023-05-18T11:00:29.22457+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:34.12592+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.041162ms 2023-05-18T11:00:34.12598+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:34.22437+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.785252ms 2023-05-18T11:00:34.22444+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:39.08733+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.906630077s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:00:39.0874+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:39.08742+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:39.08746+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.906734478s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:00:39.08747+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:39.0875+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:39.12598+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.960095ms 2023-05-18T11:00:39.12604+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:39.14108+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_disk, duration: 9.931070919s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T11:00:39.14114+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:39.14116+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_disk, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:39.14212+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_resource, duration: 9.931537212s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T11:00:39.14215+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:39.14217+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_resource, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:39.17801+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_assigned, duration: 9.993119356s (over 100ms), sql: select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ? 2023-05-18T11:00:39.17806+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:39.17807+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_assigned, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:39.18795+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_server, duration: 10.016029873s (over 100ms), sql: select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status 2023-05-18T11:00:39.188+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:39.18802+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_server, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:39.18805+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields: error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T11:00:39.198+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 10.025876902s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T11:00:39.19804+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:39.19806+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:39.19812+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 10.013731447s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T11:00:39.19815+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:39.19817+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:39.22448+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.984695ms 2023-05-18T11:00:39.22453+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:39.30848+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_unit_config, duration: 10.097971379s (over 100ms), sql: select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ? 2023-05-18T11:00:39.30853+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ?, args:[10.0.10.102], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:39.30855+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_unit_config, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:44.12605+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.770993ms 2023-05-18T11:00:44.12612+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:44.2246+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.012295ms 2023-05-18T11:00:44.22467+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:49.01296+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_index, duration: 1m39.94393906s (over 100ms), sql: select /*+ MONITOR_AGENT QUERY_TIMEOUT(100000000) */ count(*) as cnt from CDB_INDEXES where status in ('ERROR','UNUSABLE') 2023-05-18T11:00:49.01302+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /*+ MONITOR_AGENT QUERY_TIMEOUT(100000000) */ count(*) as cnt from CDB_INDEXES where status in ('ERROR','UNUSABLE'), args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 100000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:49.01304+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_index, err: Error 4012: Timeout, query has reached the maximum query timeout: 100000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:49.1263+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.042096ms 2023-05-18T11:00:49.12638+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:49.22475+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.864893ms 2023-05-18T11:00:49.22482+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:49.22486+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T11:00:54.08649+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.909737572s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:00:54.08654+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:54.08656+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:54.09611+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.920531118s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:00:54.09615+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:54.09617+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:00:54.1255+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.854293ms 2023-05-18T11:00:54.12555+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:54.22439+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.449688ms 2023-05-18T11:00:54.22445+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:59.12583+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.770992ms 2023-05-18T11:00:59.12589+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:00:59.22433+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.67969ms 2023-05-18T11:00:59.2244+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:04.12549+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.927694ms 2023-05-18T11:01:04.12556+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:04.22504+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.901594ms 2023-05-18T11:01:04.22514+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:09.12575+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.921194ms 2023-05-18T11:01:09.12581+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:09.1807+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 10.004215758s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:01:09.18075+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:09.18077+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:09.18084+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 10.004430461s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:01:09.18086+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:09.18087+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:09.22395+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.527688ms 2023-05-18T11:01:09.22401+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:09.25219+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields: error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T11:01:14.12606+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.108297ms 2023-05-18T11:01:14.12613+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:14.22466+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.860293ms 2023-05-18T11:01:14.22473+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:19.12596+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.756392ms 2023-05-18T11:01:19.12602+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:19.22456+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.742792ms 2023-05-18T11:01:19.22463+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:19.30325+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T11:01:24.12559+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.698491ms 2023-05-18T11:01:24.12566+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:24.15713+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.980942041s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:01:24.15719+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:24.15728+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:24.17664+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 10.000381005s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:01:24.17669+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:24.1767+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:24.22408+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.906194ms 2023-05-18T11:01:24.22414+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:29.13813+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.232799ms 2023-05-18T11:01:29.1382+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:29.22442+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.703591ms 2023-05-18T11:01:29.22449+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:34.12659+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.006196ms 2023-05-18T11:01:34.12666+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:34.22461+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.466902ms 2023-05-18T11:01:34.22468+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:39.12584+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.725092ms 2023-05-18T11:01:39.12591+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:39.13956+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_assigned, duration: 9.954156176s (over 100ms), sql: select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ? 2023-05-18T11:01:39.13962+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:39.13965+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_assigned, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:39.14217+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_resource, duration: 9.931105263s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T11:01:39.1422+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:39.14222+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_resource, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:39.14228+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_disk, duration: 9.931130563s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T11:01:39.14231+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:39.14233+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_disk, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:39.18015+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.994683427s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:01:39.18019+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:39.18021+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:39.18028+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.994721428s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:01:39.1803+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:39.18031+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:39.22436+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.743787ms 2023-05-18T11:01:39.22442+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:39.24035+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_server, duration: 10.073448283s (over 100ms), sql: select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status 2023-05-18T11:01:39.2404+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:39.24043+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_server, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:39.24051+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 10.054591826s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T11:01:39.24054+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:39.24056+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:39.2603+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T11:01:39.26045+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 10.093404339s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T11:01:39.26048+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:39.26049+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:39.31024+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_unit_config, duration: 10.09924748s (over 100ms), sql: select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ? 2023-05-18T11:01:39.31028+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ?, args:[10.0.10.102], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:39.3103+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_unit_config, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:44.12606+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.787887ms 2023-05-18T11:01:44.12613+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:44.22416+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.541284ms 2023-05-18T11:01:44.22423+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:49.12598+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.647685ms 2023-05-18T11:01:49.12604+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:49.22438+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.949889ms 2023-05-18T11:01:49.22446+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:49.26286+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields: error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T11:01:54.08426+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.907954352s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:01:54.08431+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:54.08433+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:54.0844+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.908162455s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:01:54.08442+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:54.08443+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:01:54.12562+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.803888ms 2023-05-18T11:01:54.12569+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:54.22462+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.581284ms 2023-05-18T11:01:54.22467+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:59.12545+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.723386ms 2023-05-18T11:01:59.12553+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:01:59.2249+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.907988ms 2023-05-18T11:01:59.22496+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:04.12568+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.659185ms 2023-05-18T11:02:04.12574+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:04.22407+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.753287ms 2023-05-18T11:02:04.22415+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:09.12541+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.440782ms 2023-05-18T11:02:09.12548+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:09.15077+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.974569108s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:02:09.15081+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:09.15083+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:09.15095+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.974819511s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:02:09.15097+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:09.15099+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:09.22454+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.826687ms 2023-05-18T11:02:09.22462+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:09.24114+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T11:02:14.12584+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.04189ms 2023-05-18T11:02:14.12591+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:14.22459+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.902189ms 2023-05-18T11:02:14.22466+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:19.12569+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.715187ms 2023-05-18T11:02:19.12576+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:19.22494+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.896988ms 2023-05-18T11:02:19.22502+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:19.26306+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields: error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T11:02:24.12594+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.868088ms 2023-05-18T11:02:24.126+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:24.13156+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.954631152s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:02:24.13161+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:24.13163+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:24.18075+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 10.004958999s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:02:24.18079+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:24.1808+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:24.22521+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.04509ms 2023-05-18T11:02:24.22526+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:28.98327+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_index, duration: 1m39.970185449s (over 100ms), sql: select /*+ MONITOR_AGENT QUERY_TIMEOUT(100000000) */ count(*) as cnt from CDB_INDEXES where status in ('ERROR','UNUSABLE') 2023-05-18T11:02:28.98334+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /*+ MONITOR_AGENT QUERY_TIMEOUT(100000000) */ count(*) as cnt from CDB_INDEXES where status in ('ERROR','UNUSABLE'), args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 100000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:28.98336+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_index, err: Error 4012: Timeout, query has reached the maximum query timeout: 100000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:29.13779+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.749487ms 2023-05-18T11:02:29.13786+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:29.22473+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.892388ms 2023-05-18T11:02:29.2248+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:34.1256+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.726387ms 2023-05-18T11:02:34.12566+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:34.22465+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.594885ms 2023-05-18T11:02:34.22472+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:39.08777+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:203:collectDBData: slow sql, duration: 9.901279467s (over 100ms), sql: SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META' 2023-05-18T11:02:39.08783+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:206:collectDBData: failed to do collect with sql SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META', args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.08785+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key jointable-1, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.09785+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_assigned, duration: 9.911186794s (over 100ms), sql: select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ? 2023-05-18T11:02:39.09789+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.09792+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_assigned, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.11093+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:203:collectDBData: slow sql, duration: 9.901100465s (over 100ms), sql: SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META' 2023-05-18T11:02:39.11097+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:206:collectDBData: failed to do collect with sql SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META', args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.11099+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key jointable-1, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.12043+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:203:collectDBData: slow sql, duration: 9.907886452s (over 100ms), sql: SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META' 2023-05-18T11:02:39.12046+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:206:collectDBData: failed to do collect with sql SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META', args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.12048+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key jointable-3, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.12635+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.841288ms 2023-05-18T11:02:39.1264+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:39.12825+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.947339259s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:02:39.12829+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.12831+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.13831+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.957319186s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:02:39.13834+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.13835+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.14095+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_disk, duration: 9.930995748s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T11:02:39.14098+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.141+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_disk, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.14755+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_resource, duration: 9.937646834s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T11:02:39.14759+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.14761+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_resource, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.18104+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:203:collectDBData: slow sql, duration: 9.994445763s (over 100ms), sql: SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META' 2023-05-18T11:02:39.18108+08:00 WARN [359133,d8742349c0f00883] caller=jointable/jointable.go:206:collectDBData: failed to do collect with sql SELECT tenant_id ob_tenant_id, tenant_name FROM DBA_OB_TENANTS WHERE tenant_type<>'META', args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.1811+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key jointable-3, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.20879+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_server, duration: 10.027914193s (over 100ms), sql: select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status 2023-05-18T11:02:39.20883+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.20885+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_server, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.20889+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T11:02:39.20903+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 10.022479223s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T11:02:39.20907+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.20908+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.20914+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 10.028317699s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T11:02:39.20917+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.20918+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.22439+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.822888ms 2023-05-18T11:02:39.22444+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:39.27888+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_unit_config, duration: 10.069113922s (over 100ms), sql: select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ? 2023-05-18T11:02:39.27893+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ?, args:[10.0.10.102], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:39.27895+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_unit_config, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:44.12655+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.96399ms 2023-05-18T11:02:44.12663+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:44.22418+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.794188ms 2023-05-18T11:02:44.22425+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:49.12591+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.798858ms 2023-05-18T11:02:49.12597+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:49.22431+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.892358ms 2023-05-18T11:02:49.22437+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:49.30604+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T11:02:54.12572+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.799458ms 2023-05-18T11:02:54.12578+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:54.16014+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.983533058s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:02:54.1602+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:54.16022+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:54.16029+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.983615656s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:02:54.16031+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:54.16032+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:02:54.22433+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.49616ms 2023-05-18T11:02:54.22441+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:59.12642+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.872758ms 2023-05-18T11:02:59.12652+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:02:59.22531+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.216756ms 2023-05-18T11:02:59.22538+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:04.12604+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.715059ms 2023-05-18T11:03:04.12612+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:04.2245+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.867558ms 2023-05-18T11:03:04.22456+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:09.12582+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.820158ms 2023-05-18T11:03:09.12589+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:09.16163+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.985191843s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:03:09.16168+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:09.16171+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:09.16177+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.985284842s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:03:09.1618+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:09.16182+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:09.19148+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields: error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T11:03:09.22404+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.740359ms 2023-05-18T11:03:09.2241+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:14.12618+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.165156ms 2023-05-18T11:03:14.12626+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:14.22406+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.58166ms 2023-05-18T11:03:14.22412+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:19.1262+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.780259ms 2023-05-18T11:03:19.12626+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:19.22451+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.503861ms 2023-05-18T11:03:19.2246+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:19.22466+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields: error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T11:03:24.12546+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.58926ms 2023-05-18T11:03:24.12552+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:24.1685+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.991941501s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:03:24.16856+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:24.1686+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:24.16867+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.992203299s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:03:24.1687+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:24.16871+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:24.22417+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.58206ms 2023-05-18T11:03:24.22423+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:29.15274+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.012796ms 2023-05-18T11:03:29.1528+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:29.22476+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.063957ms 2023-05-18T11:03:29.22483+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:34.12589+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.015457ms 2023-05-18T11:03:34.12596+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:34.22456+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.59926ms 2023-05-18T11:03:34.22464+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:39.11442+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.927280796s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:03:39.11448+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:39.1145+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:39.12565+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.932658ms 2023-05-18T11:03:39.1257+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:39.14098+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_resource, duration: 9.931096273s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T11:03:39.14103+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(max_cpu) as max_cpu, sum(min_cpu) as min_cpu, sum(max_memory) as max_memory, sum(min_memory) as min_memory from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.min_cpu, t1.max_cpu, t1.min_memory, t1.max_memory from (select unit_id, svr_ip, svr_port, sum(min_cpu) as min_cpu, sum(max_cpu) as max_cpu, sum(memory_size) as min_memory, sum(memory_size) as max_memory from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:39.14105+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_resource, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:39.14306+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_disk, duration: 9.933105961s (over 100ms), sql: select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id 2023-05-18T11:03:39.1431+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select coalesce(t1.tenant_id, -1) as tenant_id, tenant_name, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from (select t1.unit_id, t1.svr_ip, t1.svr_port, t2.tenant_id, t1.data_disk_in_use, t1.log_disk_in_use from (select unit_id, svr_ip, svr_port, sum(data_disk_in_use) as data_disk_in_use, sum(log_disk_in_use) as log_disk_in_use from v$ob_units group by unit_id ) t1 join dba_ob_units t2 on t1.unit_id = t2.unit_id) t1 join dba_ob_tenants t2 on t1.tenant_id = t2.tenant_id where tenant_type <>'meta' group by tenant_id, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:39.14313+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_disk, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:39.16445+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.97735289s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:03:39.16449+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:39.1645+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:39.19339+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_tenant_assigned, duration: 10.004199126s (over 100ms), sql: select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ? 2023-05-18T11:03:39.19344+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ t4.tenant_id, t4.tenant_name, cpu_capacity as cpu_total,cpu_assigned,mem_capacity as mem_total,mem_assigned as mem_assigned from GV$OB_SERVERS t1 JOIN (SELECT t2.tenant_id, t3.tenant_name, t2.svr_ip, t2.svr_port FROM gv$ob_units t2 left join DBA_OB_TENANTS t3 on t2.tenant_id=t3.tenant_id WHERE T3.tenant_type<>'META') t4 ON t1.svr_ip=t4.svr_ip AND t1.svr_port=t4.svr_port WHERE t1.svr_ip = ? AND t1.svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:39.19347+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_tenant_assigned, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:39.20343+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 10.031643758s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T11:03:39.20348+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:39.2035+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:39.21355+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_role, duration: 10.026109192s (over 100ms), sql: select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ? 2023-05-18T11:03:39.2136+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select (case when with_rootserver='YES' then 1 else 0 end) as with_rootserver from DBA_OB_SERVERS where svr_ip = ? and svr_port = ?, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:39.21362+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_role, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:39.21428+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T11:03:39.21441+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_server, duration: 10.04286179s (over 100ms), sql: select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status 2023-05-18T11:03:39.21444+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ group_concat(svr_ip SEPARATOR ',') as servers, status, count(1) as cnt from DBA_OB_SERVERS group by status, args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:39.21445+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_server, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:39.22457+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.65376ms 2023-05-18T11:03:39.22463+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:39.27418+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_unit_config, duration: 10.064367258s (over 100ms), sql: select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ? 2023-05-18T11:03:39.27423+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ DBA_OB_RESOURCE_POOLS.tenant_id, DBA_OB_UNIT_CONFIGS.name, DBA_OB_UNIT_CONFIGS.max_cpu, DBA_OB_UNIT_CONFIGS.min_cpu, DBA_OB_UNIT_CONFIGS.memory_size as max_memory, DBA_OB_UNIT_CONFIGS.max_iops, DBA_OB_UNIT_CONFIGS.min_iops from DBA_OB_RESOURCE_POOLS, DBA_OB_UNIT_CONFIGS, DBA_OB_UNITS where DBA_OB_RESOURCE_POOLS.unit_config_id = DBA_OB_UNIT_CONFIGS.unit_config_id and DBA_OB_UNITS.resource_pool_id = DBA_OB_RESOURCE_POOLS.resource_pool_id and DBA_OB_UNITS.svr_ip = ?, args:[10.0.10.102], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:39.27425+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_unit_config, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:44.12589+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.955858ms 2023-05-18T11:03:44.12596+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:44.22416+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.993557ms 2023-05-18T11:03:44.22422+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:49.12591+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.721559ms 2023-05-18T11:03:49.126+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:49.22478+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.827448ms 2023-05-18T11:03:49.22483+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:49.27096+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields: error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T11:03:54.08291+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 9.906684671s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:03:54.08297+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:54.083+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:54.12665+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.13975ms 2023-05-18T11:03:54.12672+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:54.17388+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 9.99774221s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:03:54.17392+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:54.17394+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:03:54.22377+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.485446ms 2023-05-18T11:03:54.22384+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:59.12646+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.99315ms 2023-05-18T11:03:59.12654+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:03:59.2245+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.856548ms 2023-05-18T11:03:59.22457+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:04:04.12599+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.929349ms 2023-05-18T11:04:04.12605+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:04:04.22504+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.116851ms 2023-05-18T11:04:04.22509+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:04:08.94086+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_index, duration: 1m39.957457703s (over 100ms), sql: select /*+ MONITOR_AGENT QUERY_TIMEOUT(100000000) */ count(*) as cnt from CDB_INDEXES where status in ('ERROR','UNUSABLE') 2023-05-18T11:04:08.94094+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /*+ MONITOR_AGENT QUERY_TIMEOUT(100000000) */ count(*) as cnt from CDB_INDEXES where status in ('ERROR','UNUSABLE'), args:[], err: Error 4012: Timeout, query has reached the maximum query timeout: 100000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:04:08.94096+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_index, err: Error 4012: Timeout, query has reached the maximum query timeout: 100000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:04:09.12574+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.901848ms 2023-05-18T11:04:09.12581+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:04:09.18238+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 10.00575836s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:04:09.18244+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:04:09.18246+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:04:09.18253+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 10.00585696s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:04:09.18255+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:04:09.18257+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. 2023-05-18T11:04:09.22491+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.752547ms 2023-05-18T11:04:09.22496+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:04:09.24372+08:00 ERROR [359133,] caller=common/observer.go:200:RefreshTask: refresh basic info failed scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields: error="scan obServerId: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T11:04:14.12651+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.891248ms 2023-05-18T11:04:14.1266+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:04:14.2246+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.992849ms 2023-05-18T11:04:14.22466+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:04:19.12642+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.168151ms 2023-05-18T11:04:19.12648+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:04:19.22436+08:00 INFO [359133,d8742349c0f00883] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.962949ms 2023-05-18T11:04:19.22442+08:00 ERROR [359133,d8742349c0f00883] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:04:19.34596+08:00 ERROR [359133,] caller=common/observer.go:208:RefreshTask: refresh observer startTime failed scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again. fields:, error="scan basic info: Error 4012: Timeout, query has reached the maximum query timeout: 10000000(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again." 2023-05-18T11:04:21.07963+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_index, duration: 12.138610058s (over 100ms), sql: select /*+ MONITOR_AGENT QUERY_TIMEOUT(100000000) */ count(*) as cnt from CDB_INDEXES where status in ('ERROR','UNUSABLE') 2023-05-18T11:04:21.07968+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /*+ MONITOR_AGENT QUERY_TIMEOUT(100000000) */ count(*) as cnt from CDB_INDEXES where status in ('ERROR','UNUSABLE'), args:[], err: invalid connection 2023-05-18T11:04:21.0797+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_index, err: invalid connection 2023-05-18T11:04:21.07978+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_all_session, duration: 6.902904141s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:04:21.0798+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(1) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: invalid connection 2023-05-18T11:04:21.07982+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_all_session, err: invalid connection 2023-05-18T11:04:21.07989+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:310:collectData: slow sql, name: ob_active_session, duration: 6.904323651s (over 100ms), sql: select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2 2023-05-18T11:04:21.07991+08:00 WARN [359133,d8742349c0f00883] caller=mysql/table_input.go:320:collectData: failed to do collect with sql select /* MONITOR_AGENT */ case when cnt is null then 0 else cnt end as cnt, tenant_name, tenant_id from (select DBA_OB_TENANTS.tenant_name, DBA_OB_TENANTS.tenant_id, cnt from DBA_OB_TENANTS left join (select count(`state`='ACTIVE' OR NULL) as cnt, tenant as tenant_name from GV$OB_PROCESSLIST where svr_ip = ? and svr_port = ? group by tenant) t1 on DBA_OB_TENANTS.tenant_name = t1.tenant_name where DBA_OB_TENANTS.tenant_type<>'META') t2, args:[10.0.10.102 2882], err: invalid connection 2023-05-18T11:04:21.07992+08:00 ERROR [359133,d8742349c0f00883] caller=common/input_cache.go:39:Update: update cache for key ob_active_session, err: invalid connection 2023-05-18T11:04:46.18126+08:00 INFO [539043,bdc7d47d6b583724] caller=stat/metrics.go:25:RegisterStat: registry with labels: map[app:HOST process:ob_monagent svr_ip:10.0.10.102] 2023-05-18T11:04:46.18236+08:00 INFO [539043,bdc7d47d6b583724] caller=stat/metrics.go:25:RegisterStat: registry with labels: map[app:HOST process:ob_monagent svr_ip:10.0.10.102] 2023-05-18T11:04:46.18334+08:00 INFO [539043,bdc7d47d6b583724] caller=sdk/monagent_callbacks.go:75:func6: module monagent.server.basic.auth init config successfully 2023-05-18T11:04:46.18519+08:00 WARN [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:119:InitPipelineModuleCallback: pipeline module config host.log is inactive or invalid, just skip 2023-05-18T11:04:46.18695+08:00 WARN [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:119:InitPipelineModuleCallback: pipeline module config trace.log is inactive or invalid, just skip 2023-05-18T11:04:46.19073+08:00 WARN [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:119:InitPipelineModuleCallback: pipeline module config monitor.ob.err.log is inactive or invalid, just skip 2023-05-18T11:04:46.19242+08:00 WARN [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:119:InitPipelineModuleCallback: pipeline module config monitor.mysql is inactive or invalid, just skip 2023-05-18T11:04:46.19831+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields: module=monitor.node.host, duration="13.1µs" 2023-05-18T11:04:46.19838+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields: duration="9.401µs", module=monitor.node.host, eventType=add 2023-05-18T11:04:46.19842+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields: module=monitor.node.host, duration="4.5µs" 2023-05-18T11:04:46.19848+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields:, module=monitor.node.host, eventType=add, duration="9.5µs" 2023-05-18T11:04:46.19852+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance nodeExporterInput 2023-05-18T11:04:46.19884+08:00 INFO [539043,] caller=collector/filesystem_common.go:110:NewFilesystemCollector: fields: fields.msg="Parsed flag --collector.filesystem.mount-points-exclude", collector=filesystem, fields.level=info, flag="^/(dev|proc|sys|var/lib/docker/.+)($|/)" 2023-05-18T11:04:46.19893+08:00 INFO [539043,] caller=collector/filesystem_common.go:112:NewFilesystemCollector: fields:, collector=filesystem, fields.level=info, fields.msg="Parsed flag --collector.filesystem.fs-types-exclude", flag="^(autofs|binfmt_misc|bpf|cgroup2?|configfs|debugfs|devpts|devtmpfs|fusectl|hugetlbfs|iso9660|mqueue|nsfs|overlay|proc|procfs|pstore|rpc_pipefs|securityfs|selinuxfs|squashfs|sysfs|tracefs)$" 2023-05-18T11:04:46.19965+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:62:init: init processor instance aggregateProcessor 2023-05-18T11:04:46.19981+08:00 INFO [539043,bdc7d47d6b583724] caller=aggregate/aggregator.go:73:Init: init aggregateProcessor with config: &{Rules:[0xc000212a80] IsRetainNativeMetric:false} 2023-05-18T11:04:46.19984+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:62:init: init processor instance attrProcessor 2023-05-18T11:04:46.20014+08:00 INFO [539043,bdc7d47d6b583724] caller=attr/attribute_operate.go:61:Init: init retagProcessor with config: {Operations:[{Oper:copyTags Condition:{Metric: Fields:map[] Tags:map[]} Tags:map[mountpoint:mount_point] RemoveItems:[]} {Oper:addTags Condition:{Metric: Fields:map[] Tags:map[]} Tags:map[app:HOST ob_cluster_id:1 ob_cluster_name:fund obproxy_cluster: obproxy_cluster_id:0 obzone:zone1 svr_ip:10.0.10.102] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:node_filesystem_size_bytes Fields:map[] Tags:map[fstype:tmpfs]} Tags:map[] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:node_filesystem_avail_bytes Fields:map[] Tags:map[fstype:tmpfs]} Tags:map[] RemoveItems:[]}]} 2023-05-18T11:04:46.20017+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:62:init: init processor instance mountLabelProcessor 2023-05-18T11:04:46.20029+08:00 INFO [539043,bdc7d47d6b583724] caller=label/mount_label.go:70:Init: init mountLabelProcessor with config: &{LabelTags:map[checkReadonly:/ dataDiskPath:/home/oceanbase/fund/oceanbase/store installPath:/home/oceanbase/fund/oceanbase logDiskPath:/home/oceanbase/fund/oceanbase/store] ObStatus:active} 2023-05-18T11:04:46.20786+08:00 INFO [539043,] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=df /home/oceanbase/fund/oceanbase, timeout=10s}, exitCode=1 fields:, duration=7.508153ms 2023-05-18T11:04:46.20791+08:00 WARN [539043,] caller=common/mount.go:22:GetMountPath: get path's mount failed, filePath: /home/oceanbase/fund/oceanbase 2023-05-18T11:04:46.2143+08:00 INFO [539043,] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=df /data/fund, timeout=10s}, exitCode=1 fields:, duration=6.373444ms 2023-05-18T11:04:46.21434+08:00 WARN [539043,] caller=common/mount.go:22:GetMountPath: get path's mount failed, filePath: /data/fund 2023-05-18T11:04:46.21763+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields: module=node.custom, duration="12.5µs" 2023-05-18T11:04:46.22751+08:00 INFO [539043,] caller=common/input_cache.go:30:Update: cache for filesystem updated firstly! 2023-05-18T11:04:46.2276+08:00 INFO [539043,] caller=common/input_cache.go:30:Update: cache for netdev updated firstly! 2023-05-18T11:04:46.22763+08:00 INFO [539043,] caller=common/input_cache.go:30:Update: cache for loadavg updated firstly! 2023-05-18T11:04:46.22835+08:00 INFO [539043,] caller=common/input_cache.go:30:Update: cache for cpu updated firstly! 2023-05-18T11:04:46.22847+08:00 INFO [539043,] caller=common/input_cache.go:30:Update: cache for diskstats updated firstly! 2023-05-18T11:04:46.22856+08:00 INFO [539043,] caller=common/input_cache.go:30:Update: cache for meminfo updated firstly! 2023-05-18T11:04:46.23742+08:00 WARN [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:119:InitPipelineModuleCallback: pipeline module config ob.log is inactive or invalid, just skip 2023-05-18T11:04:46.2383+08:00 INFO [539043,] caller=config/config_version.go:34:SetConfigMetaModuleConfigNotify: receive version backup conf: {MaxBackups:30} 2023-05-18T11:04:46.23846+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields:, module=monitor.ob, duration="11.3µs" 2023-05-18T11:04:46.23853+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields: module=log.alarm, duration="8.1µs" 2023-05-18T11:04:46.23856+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields:, module=ob.custom, duration="5.9µs" 2023-05-18T11:04:46.2386+08:00 INFO [539043,] caller=runtime/asm_amd64.s:1581:goexit: check config version backups once. 2023-05-18T11:04:46.23868+08:00 INFO [539043,] caller=config/config_version.go:89:checkConfigVersionBackups: read config from path /home/oceanbase/fund/obagent/conf, files length 11 2023-05-18T11:04:46.23871+08:00 INFO [539043,] caller=config/config_version.go:105:checkConfigVersionBackups: config stay count:30, config version count:1, no need to rotate. 2023-05-18T11:04:46.2394+08:00 INFO [539043,] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=df /data/fund, timeout=10s}, exitCode=1 fields: duration=25.042976ms 2023-05-18T11:04:46.23944+08:00 WARN [539043,] caller=common/mount.go:22:GetMountPath: get path's mount failed, filePath: /data/fund 2023-05-18T11:04:46.24562+08:00 INFO [539043,] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=df /, timeout=10s}, exitCode=1 fields:, duration=6.163944ms 2023-05-18T11:04:46.24565+08:00 WARN [539043,] caller=common/mount.go:22:GetMountPath: get path's mount failed, filePath: / 2023-05-18T11:04:46.25162+08:00 INFO [539043,] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=df -h, timeout=10s}, exitCode=1 fields:, duration=5.923542ms 2023-05-18T11:04:46.25166+08:00 WARN [539043,bdc7d47d6b583724] caller=label/mount_label.go:187:getMountPV: execute cmd df -h failed, err: failed to execute command: Command{user=admin, program=sh, outputType=combined, cmd=df -h, timeout=10s}, exitCode: 1, output: 2023-05-18T11:04:46.25167+08:00 WARN [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:68:init: get mountPV failed 2023-05-18T11:04:46.25169+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:90:init: init exporter instance prometheusExporter 2023-05-18T11:04:46.25179+08:00 INFO [539043,bdc7d47d6b583724] caller=prometheus/prometheus.go:78:Init: prometheus exporter config: &{FormatType:fmtText ExposeUrl: WithTimestamp:true} 2023-05-18T11:04:46.25181+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields:, module=monitor.node.host, eventType=add, duration=53.338775ms 2023-05-18T11:04:46.25183+08:00 INFO [539043,bdc7d47d6b583724] caller=monagent/monagent_route.go:77:RegisterPipelineRoute: register route /metrics/node/host 2023-05-18T11:04:46.25187+08:00 INFO [539043,bdc7d47d6b583724] caller=monagent/monagent_route.go:77:RegisterPipelineRoute: register route /metrics/node/host 2023-05-18T11:04:46.25189+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields: module=monitor.node.host, duration=53.471076ms 2023-05-18T11:04:46.2519+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields: module=monitor.node.host, eventType=add, duration=53.535977ms 2023-05-18T11:04:46.25192+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields:, module=node.custom, eventType=add, duration="4.7µs" 2023-05-18T11:04:46.25194+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields:, module=node.custom, duration="3.3µs" 2023-05-18T11:04:46.25197+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields: module=node.custom, duration="4.2µs", eventType=add 2023-05-18T11:04:46.252+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance hostCustomInput 2023-05-18T11:04:46.25246+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance processInput 2023-05-18T11:04:46.25257+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:62:init: init processor instance attrProcessor 2023-05-18T11:04:46.25289+08:00 INFO [539043,bdc7d47d6b583724] caller=attr/attribute_operate.go:61:Init: init retagProcessor with config: {Operations:[{Oper:copyTags Condition:{Metric: Fields:map[] Tags:map[]} Tags:map[dev:device] RemoveItems:[]} {Oper:addTags Condition:{Metric: Fields:map[] Tags:map[]} Tags:map[app:HOST ob_cluster_id:1 ob_cluster_name:fund obproxy_cluster: obproxy_cluster_id:0 obzone:zone1 svr_ip:10.0.10.102] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:observer_coredump_time_seconds Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:observer_ulimit_max_fd_count Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:observer_fd_count Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:ob_log_disk_writable Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:ob_data_disk_writable Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]}]} 2023-05-18T11:04:46.25291+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:62:init: init processor instance mountLabelProcessor 2023-05-18T11:04:46.25298+08:00 INFO [539043,bdc7d47d6b583724] caller=label/mount_label.go:70:Init: init mountLabelProcessor with config: &{LabelTags:map[dataDiskPath:/home/oceanbase/fund/oceanbase/store logDiskPath:/home/oceanbase/fund/oceanbase/store] ObStatus:active} 2023-05-18T11:04:46.25898+08:00 INFO [539043,] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=df ., timeout=10s}, exitCode=1 fields: duration=5.949342ms 2023-05-18T11:04:46.25901+08:00 WARN [539043,] caller=common/mount.go:22:GetMountPath: get path's mount failed, filePath: . 2023-05-18T11:04:46.26271+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:38:addPipeline: add pipeline module config result status: succeed, description: fields: module=monitor.node.host, duration=64.412753ms 2023-05-18T11:04:46.26276+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:126:func1: add pipeline module config monitor.node.host successfully. 2023-05-18T11:04:46.26498+08:00 INFO [539043,] caller=common/input_cache.go:30:Update: cache for cpu_count updated firstly! 2023-05-18T11:04:46.26513+08:00 INFO [539043,] caller=common/input_cache.go:30:Update: cache for io_infos updated firstly! 2023-05-18T11:04:46.28844+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=ethtool lo, timeout=50s}, exitCode=1 fields:, duration=24.985676ms 2023-05-18T11:04:46.2885+08:00 WARN [539043,bdc7d47d6b583724] caller=host/custom.go:475:doCollectBandwidthInfo: get bandwidth of net interface lo failed, cmd: ethtool lo 2023-05-18T11:04:46.29505+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=ethtool eth0, timeout=50s}, exitCode=1 fields:, duration=6.535846ms 2023-05-18T11:04:46.29511+08:00 WARN [539043,bdc7d47d6b583724] caller=host/custom.go:475:doCollectBandwidthInfo: get bandwidth of net interface eth0 failed, cmd: ethtool eth0 2023-05-18T11:04:46.29513+08:00 INFO [539043,] caller=common/input_cache.go:30:Update: cache for bandwidth_infos updated firstly! 2023-05-18T11:04:46.29518+08:00 INFO [539043,] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=df /data/fund, timeout=10s}, exitCode=1 fields:, duration=36.147154ms 2023-05-18T11:04:46.29521+08:00 WARN [539043,] caller=common/mount.go:22:GetMountPath: get path's mount failed, filePath: /data/fund 2023-05-18T11:04:46.30107+08:00 INFO [539043,] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=df /data/fund, timeout=10s}, exitCode=1 fields: duration=5.833141ms 2023-05-18T11:04:46.30112+08:00 WARN [539043,] caller=common/mount.go:22:GetMountPath: get path's mount failed, filePath: /data/fund 2023-05-18T11:04:46.30115+08:00 WARN [539043,] caller=common/mount.go:15:GetMountPath: check filepath stat failed, err: stat : no such file or directory 2023-05-18T11:04:46.30713+08:00 INFO [539043,] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=df -h, timeout=10s}, exitCode=1 fields:, duration=5.924341ms 2023-05-18T11:04:46.30717+08:00 WARN [539043,bdc7d47d6b583724] caller=label/mount_label.go:187:getMountPV: execute cmd df -h failed, err: failed to execute command: Command{user=admin, program=sh, outputType=combined, cmd=df -h, timeout=10s}, exitCode: 1, output: 2023-05-18T11:04:46.30718+08:00 WARN [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:68:init: get mountPV failed 2023-05-18T11:04:46.30719+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:90:init: init exporter instance prometheusExporter 2023-05-18T11:04:46.3073+08:00 INFO [539043,bdc7d47d6b583724] caller=prometheus/prometheus.go:78:Init: prometheus exporter config: &{FormatType:fmtText ExposeUrl: WithTimestamp:false} 2023-05-18T11:04:46.30732+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields: duration=55.35629ms, module=node.custom, eventType=add 2023-05-18T11:04:46.30734+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields:, module=node.custom, duration=55.40649ms 2023-05-18T11:04:46.30736+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields:, module=node.custom, eventType=add, duration=55.43879ms 2023-05-18T11:04:46.30738+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields:, module=monitor.ob, eventType=add, duration="6µs" 2023-05-18T11:04:46.30739+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields:, module=monitor.ob, duration="3.9µs" 2023-05-18T11:04:46.30742+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields: module=monitor.ob, eventType=add, duration="4µs" 2023-05-18T11:04:46.30745+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T11:04:46.31253+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc0003505a0 0xc000350640 0xc0003506e0 0xc000350780 0xc000350820 0xc0003508c0 0xc000350960 0xc000350a00 0xc000350aa0 0xc000350b40 0xc000350be0 0xc000350c80 0xc000350d20 0xc000350dc0 0xc000350e60 0xc000350f00 0xc000350fa0 0xc000351040 0xc0003510e0 0xc000351180 0xc000351220 0xc0003512c0 0xc000351360 0xc000351400 0xc0003514a0 0xc000351540 0xc0003515e0 0xc000351680 0xc000351720 0xc0003517c0 0xc000351860] CollectInterval:1s TimeAlign:false} 2023-05-18T11:04:46.31356+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:38:addPipeline: add pipeline module config result status: succeed, description: fields: module=node.custom, duration=95.946674ms 2023-05-18T11:04:46.31362+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:126:func1: add pipeline module config node.custom successfully. 2023-05-18T11:04:46.34521+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T11:04:46.34525+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields: duration="10.7µs", input=mysqlTableInput 2023-05-18T11:04:46.3453+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields: input=mysqlTableInput, duration="53.201µs" 2023-05-18T11:04:46.34533+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields: module=monitor.ob, eventType=add, error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)", duration=37.913067ms 2023-05-18T11:04:46.34536+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields: duration=37.937667ms, module=monitor.ob, eventType=add 2023-05-18T11:04:46.34538+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields: duration=37.995167ms, module=monitor.ob 2023-05-18T11:04:46.3454+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields:, module=monitor.ob, eventType=add, duration=38.030967ms 2023-05-18T11:04:46.34544+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields: module=log.alarm, eventType=add, duration="6µs" 2023-05-18T11:04:46.34575+08:00 INFO [539043,] caller=inputs/all.go:60:func7: configData: {Timeout:1m0s PluginInnerConfig:map[recoveryConfig:map[enabled:true triggerThreshold:10000] tailConfigs:[map[logAnalyzerType:host_light logDir:/var/log logFileName:kern logSourceType:kern processLogInterval:500ms] map[logAnalyzerType:agent_light logDir:/home/oceanbase/fund/obagent/log logFileName:monagent.log logSourceType:monagent_log processLogInterval:500ms] map[logAnalyzerType:agent_light logDir:/home/oceanbase/fund/obagent/log logFileName:mgragent.log logSourceType:mgragent_log processLogInterval:500ms] map[logAnalyzerType:ob logDir:/home/oceanbase/fund/oceanbase/log logFileName:rootservice.log.wf logSourceType:rootservice processLogInterval:500ms] map[logAnalyzerType:ob logDir:/home/oceanbase/fund/oceanbase/log logFileName:election.log.wf logSourceType:election processLogInterval:500ms] map[logAnalyzerType:ob logDir:/home/oceanbase/fund/oceanbase/log logFileName:observer.log.wf logSourceType:observer processLogInterval:500ms]]]} 2023-05-18T11:04:46.34609+08:00 INFO [539043,] caller=inputs/all.go:71:func7: logTailerInput config: {TailConfigs:[{LogDir:/var/log LogFileName:kern ProcessLogInterval:500ms LogSourceType:kern LogAnalyzerType:host_light} {LogDir:/home/oceanbase/fund/obagent/log LogFileName:monagent.log ProcessLogInterval:500ms LogSourceType:monagent_log LogAnalyzerType:agent_light} {LogDir:/home/oceanbase/fund/obagent/log LogFileName:mgragent.log ProcessLogInterval:500ms LogSourceType:mgragent_log LogAnalyzerType:agent_light} {LogDir:/home/oceanbase/fund/oceanbase/log LogFileName:rootservice.log.wf ProcessLogInterval:500ms LogSourceType:rootservice LogAnalyzerType:ob} {LogDir:/home/oceanbase/fund/oceanbase/log LogFileName:election.log.wf ProcessLogInterval:500ms LogSourceType:election LogAnalyzerType:ob} {LogDir:/home/oceanbase/fund/oceanbase/log LogFileName:observer.log.wf ProcessLogInterval:500ms LogSourceType:observer LogAnalyzerType:ob}] RecoveryConfig:{Enabled:true LastPositionStoreDir: TriggerStoreThreshold:10000} ProcessQueueCapacity:0} 2023-05-18T11:04:46.34636+08:00 INFO [539043,] caller=retag/retag.go:63:Init: init retagProcessor with config: &{RenameTags:map[] CopyTags:map[] NewTags:map[alarmType:ob_log_alarm ip:10.0.10.102 obClusterId:1 obClusterName:fund]} 2023-05-18T11:04:46.34646+08:00 INFO [539043,] caller=outputs/all.go:52:func6: configData: map[alarmTimeWindow:3m keywordAlarmRules: logAlarmFilters:[] logFilterRulesJsonContent: logSourceType2AlarmType:map[election:election_log_alarm kern:message_log_alarm mgragent_log:mgragent_log_alarm monagent_log:monagent_log_alarm obproxy_error:obproxy_log_alarm observer:observer_log_alarm rootservice:rootservice_log_alarm]] 2023-05-18T11:04:46.3466+08:00 INFO [539043,] caller=outputs/all.go:63:func6: alarmsCacheOutput config: &{LogFilterRulesJsonContent: LogAlarmFilters:[] AlarmTimeWindow:3m0s LogSourceType2AlarmType:map[election:election_log_alarm kern:message_log_alarm mgragent_log:mgragent_log_alarm monagent_log:monagent_log_alarm obproxy_error:obproxy_log_alarm observer:observer_log_alarm rootservice:rootservice_log_alarm]} 2023-05-18T11:04:46.34664+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields: module=log.alarm, duration=1.181008ms 2023-05-18T11:04:46.34704+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields: module=monitor.ob, duration=108.594164ms 2023-05-18T11:04:46.34708+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 0 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T11:04:46.34709+08:00 INFO [539043,] caller=monagent/monagent_route.go:77:RegisterPipelineRoute: register route /api/v1/log/alarms 2023-05-18T11:04:46.34713+08:00 INFO [539043,] caller=monagent/monagent_route.go:77:RegisterPipelineRoute: register route /api/v1/log/alarms 2023-05-18T11:04:46.34715+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields:, module=log.alarm, eventType=add, duration="4.5µs" 2023-05-18T11:04:46.34718+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:211:func3: start pipelineV2 log_tailer_to_alarm 2023-05-18T11:04:46.34721+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields: eventType=add, duration="63.8µs", module=log.alarm 2023-05-18T11:04:46.34724+08:00 INFO [539043,] caller=log_tailer/log_tailer.go:48:Start: start to run log tailer 2023-05-18T11:04:46.34729+08:00 ERROR [539043,] caller=log_tailer/log_tailer.go:77:Run: loadLastPosition failed fields:, tailConf="{/var/log kern 500ms kern host_light}", error="invalid argument" 2023-05-18T11:04:46.34732+08:00 INFO [539043,] caller=log_tailer/log_tailer.go:77:Run: build fileProcessQueueMap with initLogQueue fields: initLogQueue="[]", tailConf="{/var/log kern 500ms kern host_light}" 2023-05-18T11:04:46.34749+08:00 INFO [539043,] caller=log_tailer/log_tailer_utils.go:210:getLogsWithinTime: invoke FindFilesByRegexAndMTime fields: fileName=monagent.log, start="2023-04-29 13:49:15.24073 +0800 CST", end="2023-05-18 11:04:46.347423625 +0800 CST m=+0.194456169", dir=/home/oceanbase/fund/obagent/log, matchedFiles="[0xc000a78750]" 2023-05-18T11:04:46.34753+08:00 INFO [539043,] caller=log_tailer/log_tailer_recovery.go:99:loadLastPosition: getLogsWithinTime match file fields:, matchedFileRealPath=/home/oceanbase/fund/obagent/log/monagent.log 2023-05-18T11:04:46.34755+08:00 INFO [539043,] caller=log_tailer/log_tailer.go:77:Run: build fileProcessQueueMap with initLogQueue fields: tailConf="{/home/oceanbase/fund/obagent/log monagent.log 500ms monagent_log agent_light}", initLogQueue="[0xc0009ed440]" 2023-05-18T11:04:46.34761+08:00 ERROR [539043,] caller=log_tailer/log_tailer.go:77:Run: loadLastPosition failed fields: error="invalid argument", tailConf="{/home/oceanbase/fund/obagent/log mgragent.log 500ms mgragent_log agent_light}" 2023-05-18T11:04:46.34764+08:00 INFO [539043,] caller=log_tailer/log_tailer.go:77:Run: build fileProcessQueueMap with initLogQueue fields:, initLogQueue="[]", tailConf="{/home/oceanbase/fund/obagent/log mgragent.log 500ms mgragent_log agent_light}" 2023-05-18T11:04:46.34766+08:00 ERROR [539043,] caller=log_tailer/log_tailer.go:77:Run: loadLastPosition failed fields: error="invalid argument", tailConf="{/home/oceanbase/fund/oceanbase/log rootservice.log.wf 500ms rootservice ob}" 2023-05-18T11:04:46.34768+08:00 INFO [539043,] caller=log_tailer/log_tailer.go:77:Run: build fileProcessQueueMap with initLogQueue fields: tailConf="{/home/oceanbase/fund/oceanbase/log rootservice.log.wf 500ms rootservice ob}", initLogQueue="[]" 2023-05-18T11:04:46.3477+08:00 ERROR [539043,] caller=log_tailer/log_tailer.go:77:Run: loadLastPosition failed fields: error="invalid argument", tailConf="{/home/oceanbase/fund/oceanbase/log election.log.wf 500ms election ob}" 2023-05-18T11:04:46.34772+08:00 INFO [539043,] caller=log_tailer/log_tailer.go:77:Run: build fileProcessQueueMap with initLogQueue fields:, tailConf="{/home/oceanbase/fund/oceanbase/log election.log.wf 500ms election ob}", initLogQueue="[]" 2023-05-18T11:04:46.34774+08:00 ERROR [539043,] caller=log_tailer/log_tailer.go:77:Run: loadLastPosition failed fields: tailConf="{/home/oceanbase/fund/oceanbase/log observer.log.wf 500ms observer ob}", error="invalid argument" 2023-05-18T11:04:46.34775+08:00 INFO [539043,] caller=log_tailer/log_tailer.go:77:Run: build fileProcessQueueMap with initLogQueue fields:, initLogQueue="[]", tailConf="{/home/oceanbase/fund/oceanbase/log observer.log.wf 500ms observer ob}" 2023-05-18T11:04:46.34778+08:00 INFO [539043,] caller=log_tailer/log_tailer_executor.go:193:WatchFile: start watching fields:, fileRealPath=/home/oceanbase/fund/oceanbase/log/observer.log.wf 2023-05-18T11:04:46.34779+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields: module=log.alarm, duration=2.340016ms 2023-05-18T11:04:46.34781+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields: module=log.alarm, eventType=add, duration=2.377416ms 2023-05-18T11:04:46.34782+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields:, eventType=add, module=ob.custom, duration="3.6µs" 2023-05-18T11:04:46.34783+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields:, module=ob.custom, duration="3.6µs" 2023-05-18T11:04:46.34786+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields: eventType=add, duration="4.3µs", module=ob.custom 2023-05-18T11:04:46.34788+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance dbConnectivityInput 2023-05-18T11:04:46.34798+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance processInput 2023-05-18T11:04:46.34807+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance hostCustomInput 2023-05-18T11:04:46.34851+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:62:init: init processor instance attrProcessor 2023-05-18T11:04:46.3488+08:00 INFO [539043,bdc7d47d6b583724] caller=attr/attribute_operate.go:61:Init: init retagProcessor with config: {Operations:[{Oper:addTags Condition:{Metric: Fields:map[] Tags:map[]} Tags:map[app:OB ob_cluster_id:1 ob_cluster_name:fund obzone:zone1 svr_ip:10.0.10.102 svr_port:2882] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:io_util Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:io_await Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:node_net_bandwidth_bps Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:node_ntp_offset_seconds Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:ssd_wear_indicator Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:tcp_retrans Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]} {Oper:removeMetric Condition:{Metric:cpu_count Fields:map[] Tags:map[]} Tags:map[] RemoveItems:[]}]} 2023-05-18T11:04:46.34883+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:90:init: init exporter instance prometheusExporter 2023-05-18T11:04:46.34887+08:00 INFO [539043,bdc7d47d6b583724] caller=prometheus/prometheus.go:78:Init: prometheus exporter config: &{FormatType:fmtText ExposeUrl: WithTimestamp:false} 2023-05-18T11:04:46.34889+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields:, eventType=add, module=ob.custom, duration=1.038807ms 2023-05-18T11:04:46.34893+08:00 INFO [539043,] caller=log_tailer/log_tailer_executor.go:193:WatchFile: start watching fields:, fileRealPath=/var/log/kern 2023-05-18T11:04:46.349+08:00 INFO [539043,] caller=log_tailer/log_tailer_executor.go:193:WatchFile: start watching fields:, fileRealPath=/home/oceanbase/fund/obagent/log/monagent.log 2023-05-18T11:04:46.34903+08:00 INFO [539043,] caller=log_tailer/log_tailer_executor.go:193:WatchFile: start watching fields:, fileRealPath=/home/oceanbase/fund/obagent/log/mgragent.log 2023-05-18T11:04:46.34905+08:00 INFO [539043,] caller=log_tailer/log_tailer_executor.go:193:WatchFile: start watching fields:, fileRealPath=/home/oceanbase/fund/oceanbase/log/rootservice.log.wf 2023-05-18T11:04:46.34908+08:00 INFO [539043,] caller=log_tailer/log_tailer_executor.go:193:WatchFile: start watching fields:, fileRealPath=/home/oceanbase/fund/oceanbase/log/election.log.wf 2023-05-18T11:04:46.34909+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:38:addPipeline: add pipeline module config result status: succeed, description: fields:, module=log.alarm, duration=110.572677ms 2023-05-18T11:04:46.34911+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:126:func1: add pipeline module config log.alarm successfully. 2023-05-18T11:04:46.34946+08:00 INFO [539043,] caller=common/input_cache.go:30:Update: cache for io_infos updated firstly! 2023-05-18T11:04:46.35133+08:00 INFO [539043,] caller=common/input_cache.go:30:Update: cache for cpu_count updated firstly! 2023-05-18T11:04:46.35799+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=ethtool lo, timeout=50s}, exitCode=1 fields:, duration=6.547046ms 2023-05-18T11:04:46.35803+08:00 WARN [539043,bdc7d47d6b583724] caller=host/custom.go:475:doCollectBandwidthInfo: get bandwidth of net interface lo failed, cmd: ethtool lo 2023-05-18T11:04:46.36475+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=combined, cmd=ethtool eth0, timeout=50s}, exitCode=1 fields:, duration=6.707247ms 2023-05-18T11:04:46.36479+08:00 WARN [539043,bdc7d47d6b583724] caller=host/custom.go:475:doCollectBandwidthInfo: get bandwidth of net interface eth0 failed, cmd: ethtool eth0 2023-05-18T11:04:46.36481+08:00 INFO [539043,] caller=common/input_cache.go:30:Update: cache for bandwidth_infos updated firstly! 2023-05-18T11:04:46.36483+08:00 INFO [539043,bdc7d47d6b583724] caller=monagent/monagent_route.go:77:RegisterPipelineRoute: register route /metrics/node/ob 2023-05-18T11:04:46.36486+08:00 INFO [539043,bdc7d47d6b583724] caller=monagent/monagent_route.go:77:RegisterPipelineRoute: register route /metrics/node/ob 2023-05-18T11:04:46.36487+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields: duration=17.04092ms, module=ob.custom 2023-05-18T11:04:46.36489+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields: eventType=add, duration=17.07032ms, module=ob.custom 2023-05-18T11:04:46.3649+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:38:addPipeline: add pipeline module config result status: succeed, description: fields:, module=ob.custom, duration=126.342889ms 2023-05-18T11:04:46.36494+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:126:func1: add pipeline module config ob.custom successfully. 2023-05-18T11:04:46.38581+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 538719 fields:, error="open /proc/538719/status: no such file or directory" 2023-05-18T11:04:46.38585+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 538740 fields: error="open /proc/538740/status: no such file or directory" 2023-05-18T11:04:46.39281+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.671647ms 2023-05-18T11:04:46.39287+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:04:46.39289+08:00 INFO [539043,] caller=common/input_cache.go:30:Update: cache for node_ntp_offset_seconds updated firstly! 2023-05-18T11:04:46.39295+08:00 INFO [539043,] caller=common/input_cache.go:30:Update: cache for process updated firstly! 2023-05-18T11:04:46.39299+08:00 INFO [539043,] caller=common/input_cache.go:30:Update: cache for process updated firstly! 2023-05-18T11:04:46.39945+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.424645ms 2023-05-18T11:04:46.3995+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:04:46.39951+08:00 INFO [539043,] caller=common/input_cache.go:30:Update: cache for node_ntp_offset_seconds updated firstly! 2023-05-18T11:04:46.40069+08:00 ERROR [539043,43fa75edcf576df2] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:04:46.40073+08:00 INFO [539043,] caller=common/input_cache.go:30:Update: cache for oceanbase_connectivity updated firstly! 2023-05-18T11:04:46.84794+08:00 INFO [539043,] caller=log_tailer/log_tailer_executor.go:227:WatchFile: add logFileInfo to empty queue fields:, fileRealPath=/home/oceanbase/fund/oceanbase/log/observer.log.wf 2023-05-18T11:04:46.84919+08:00 INFO [539043,] caller=log_tailer/log_tailer_executor.go:227:WatchFile: add logFileInfo to empty queue fields: fileRealPath=/home/oceanbase/fund/obagent/log/mgragent.log 2023-05-18T11:04:46.84925+08:00 INFO [539043,] caller=log_tailer/log_tailer_executor.go:227:WatchFile: add logFileInfo to empty queue fields:, fileRealPath=/home/oceanbase/fund/oceanbase/log/rootservice.log.wf 2023-05-18T11:04:46.8493+08:00 INFO [539043,] caller=log_tailer/log_tailer_executor.go:227:WatchFile: add logFileInfo to empty queue fields:, fileRealPath=/home/oceanbase/fund/oceanbase/log/election.log.wf 2023-05-18T11:04:47.15792+08:00 INFO [539043,] caller=shell/exec.go:88:execute: execute shell command start, command=Command{user=oceanbase, program=sh, outputType=std, cmd=netstat -tunlp 2>/dev/null | { grep '539043/' || true; }, timeout=10s} fields:, duration="30.9µs" 2023-05-18T11:04:47.17+08:00 INFO [539043,] caller=shell/exec.go:127:execute: execute shell command end, command=Command{user=oceanbase, program=sh, outputType=std, cmd=netstat -tunlp 2>/dev/null | { grep '539043/' || true; }, timeout=10s} fields: duration=12.111485ms 2023-05-18T11:04:51.40613+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.079743ms 2023-05-18T11:04:51.40619+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:04:51.40628+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.82559ms 2023-05-18T11:04:51.40631+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:04:56.40611+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.065237ms 2023-05-18T11:04:56.40617+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:04:56.40626+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.915961ms 2023-05-18T11:04:56.40629+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:01.40673+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.190318ms 2023-05-18T11:05:01.4068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:01.40688+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.112933ms 2023-05-18T11:05:01.40691+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:06.40657+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.024242ms 2023-05-18T11:05:06.40665+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:06.40674+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.038144ms 2023-05-18T11:05:06.40679+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:11.40587+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.449127ms 2023-05-18T11:05:11.40592+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:11.40596+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.167422ms 2023-05-18T11:05:11.40599+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:16.34722+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields:, module=monitor.ob, duration="24.796µs" 2023-05-18T11:05:16.34728+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields: module=monitor.ob, eventType=add, duration="6.399µs" 2023-05-18T11:05:16.34731+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields:, module=monitor.ob, duration="4.599µs" 2023-05-18T11:05:16.34735+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields:, module=monitor.ob, eventType=add, duration="4.5µs" 2023-05-18T11:05:16.34738+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T11:05:16.35125+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc000246500 0xc0002465a0 0xc000246640 0xc0002466e0 0xc000246780 0xc000246820 0xc0002468c0 0xc000246960 0xc000246a00 0xc000246aa0 0xc000246b40 0xc000246be0 0xc000246c80 0xc000246d20 0xc000246dc0 0xc000246e60 0xc000246f00 0xc000246fa0 0xc000247040 0xc0002470e0 0xc000247180 0xc000247220 0xc0002472c0 0xc000247360 0xc000247400 0xc0002474a0 0xc000247540 0xc0002475e0 0xc000247680 0xc000247720 0xc0002477c0] CollectInterval:1s TimeAlign:false} 2023-05-18T11:05:16.35203+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T11:05:16.35206+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields: input=mysqlTableInput, duration="4.299µs" 2023-05-18T11:05:16.35207+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields: input=mysqlTableInput, duration="22.396µs" 2023-05-18T11:05:16.35209+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields: duration=4.745825ms, module=monitor.ob, eventType=add, error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:05:16.35211+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields: duration=4.765922ms, module=monitor.ob, eventType=add 2023-05-18T11:05:16.35213+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields:, module=monitor.ob, duration=4.831212ms 2023-05-18T11:05:16.35215+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields: eventType=add, duration=4.870506ms, module=monitor.ob 2023-05-18T11:05:16.35216+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields:, module=monitor.ob, duration=4.963393ms 2023-05-18T11:05:16.35218+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 1 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T11:05:16.40069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.824528ms 2023-05-18T11:05:16.40075+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:16.40224+08:00 ERROR [539043,b16e2bcf76683c1a] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:05:16.40651+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.289804ms 2023-05-18T11:05:16.40656+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:21.40732+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.007944ms 2023-05-18T11:05:21.40738+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:21.40745+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.210477ms 2023-05-18T11:05:21.40748+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:26.40567+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.391036ms 2023-05-18T11:05:26.40573+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:26.40637+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.126628ms 2023-05-18T11:05:26.40642+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:31.40695+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=5.964751ms 2023-05-18T11:05:31.40701+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:31.40709+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.521975ms 2023-05-18T11:05:31.40713+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:36.40538+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=5.720886ms 2023-05-18T11:05:36.40545+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:36.40551+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.382537ms 2023-05-18T11:05:36.40554+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:41.40423+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.612952ms 2023-05-18T11:05:41.4043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:41.40681+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=5.979986ms 2023-05-18T11:05:41.40686+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:46.42505+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.88524ms 2023-05-18T11:05:46.42512+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:46.42517+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.480949ms 2023-05-18T11:05:46.42521+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:46.45539+08:00 ERROR [539043,59868f463d980650] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:05:51.40632+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.149088ms 2023-05-18T11:05:51.40638+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:51.40646+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.024286ms 2023-05-18T11:05:51.40649+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:56.40564+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=5.866984ms 2023-05-18T11:05:56.40571+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:05:56.40576+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.66928ms 2023-05-18T11:05:56.40578+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:01.40529+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=5.607619ms 2023-05-18T11:06:01.40535+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:01.4054+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.330541ms 2023-05-18T11:06:01.40543+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:06.40684+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=5.986754ms 2023-05-18T11:06:06.40691+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:06.40698+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.011004ms 2023-05-18T11:06:06.40701+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:11.40581+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=5.817639ms 2023-05-18T11:06:11.40587+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:11.40592+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.847589ms 2023-05-18T11:06:11.40595+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:16.35307+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields: module=monitor.ob, duration="24.002µs" 2023-05-18T11:06:16.35313+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields: module=monitor.ob, eventType=add, duration="6.5µs" 2023-05-18T11:06:16.35316+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields: module=monitor.ob, duration="4.501µs" 2023-05-18T11:06:16.35319+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields: module=monitor.ob, eventType=add, duration="4.601µs" 2023-05-18T11:06:16.35323+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T11:06:16.35944+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc0006c8780 0xc0006c8820 0xc0006c88c0 0xc0006c8960 0xc0006c8a00 0xc0006c8aa0 0xc0006c8b40 0xc0006c8be0 0xc0006c8c80 0xc0006c8d20 0xc0006c8dc0 0xc0006c8e60 0xc0006c8f00 0xc0006c8fa0 0xc0006c9040 0xc0006c90e0 0xc0006c9180 0xc0006c9220 0xc0006c92c0 0xc0006c9360 0xc0006c9400 0xc0006c94a0 0xc0006c9540 0xc0006c95e0 0xc0006c9680 0xc0006c9720 0xc0006c97c0 0xc0006c9860 0xc0006c9900 0xc0006c99a0 0xc0006c9a40] CollectInterval:1s TimeAlign:false} 2023-05-18T11:06:16.36255+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T11:06:16.3626+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields: input=mysqlTableInput, duration="5.5µs" 2023-05-18T11:06:16.36262+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields:, input=mysqlTableInput, duration="27.202µs" 2023-05-18T11:06:16.36264+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields: duration=9.455276ms, error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)", module=monitor.ob, eventType=add 2023-05-18T11:06:16.36266+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields: module=monitor.ob, eventType=add, duration=9.475077ms 2023-05-18T11:06:16.36269+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields:, module=monitor.ob, duration=9.533383ms 2023-05-18T11:06:16.3627+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields:, module=monitor.ob, eventType=add, duration=9.572486ms 2023-05-18T11:06:16.36272+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields:, module=monitor.ob, duration=9.665894ms 2023-05-18T11:06:16.36274+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 2 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T11:06:16.40576+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.503858ms 2023-05-18T11:06:16.40581+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:16.40586+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=5.970753ms 2023-05-18T11:06:16.40589+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:16.40703+08:00 ERROR [539043,c25cd8402254fd40] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:06:21.40707+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.605311ms 2023-05-18T11:06:21.40716+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:21.40723+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.375138ms 2023-05-18T11:06:21.40726+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:26.40644+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=5.977453ms 2023-05-18T11:06:26.40652+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:26.40663+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.821187ms 2023-05-18T11:06:26.40666+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:31.40608+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.104565ms 2023-05-18T11:06:31.40614+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:31.40619+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.120414ms 2023-05-18T11:06:31.40622+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:36.39982+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.838533ms 2023-05-18T11:06:36.39989+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:36.40587+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=5.957451ms 2023-05-18T11:06:36.40592+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:41.40553+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=5.740031ms 2023-05-18T11:06:41.4056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:41.40565+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.582765ms 2023-05-18T11:06:41.40569+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:46.43298+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.073213ms 2023-05-18T11:06:46.43305+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:46.4331+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=26.722773ms 2023-05-18T11:06:46.43312+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:46.44726+08:00 ERROR [539043,7521132926f6ad6c] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:06:51.40653+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.297982ms 2023-05-18T11:06:51.40661+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:51.40669+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.901495ms 2023-05-18T11:06:51.40673+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:56.40641+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.121186ms 2023-05-18T11:06:56.40648+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:06:56.40653+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.445289ms 2023-05-18T11:06:56.40656+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:01.40615+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.328089ms 2023-05-18T11:07:01.40621+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:01.40626+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.171185ms 2023-05-18T11:07:01.40629+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:06.40616+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=5.881629ms 2023-05-18T11:07:06.40622+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:06.40628+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.641863ms 2023-05-18T11:07:06.40632+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:11.40557+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=5.845529ms 2023-05-18T11:07:11.40565+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:11.40572+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.631663ms 2023-05-18T11:07:11.40575+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:16.40664+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.957364ms 2023-05-18T11:07:16.4067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:16.40676+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.393832ms 2023-05-18T11:07:16.40679+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:16.40791+08:00 ERROR [539043,725295de2f679021] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:07:21.40522+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=5.630528ms 2023-05-18T11:07:21.40529+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:21.40535+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.264562ms 2023-05-18T11:07:21.40538+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:26.40695+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.148431ms 2023-05-18T11:07:26.40703+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:26.40712+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.557668ms 2023-05-18T11:07:26.40715+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:31.40609+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=5.98383ms 2023-05-18T11:07:31.40616+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:31.4062+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.140866ms 2023-05-18T11:07:31.40623+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:36.39944+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.348332ms 2023-05-18T11:07:36.3995+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:36.40545+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=5.89423ms 2023-05-18T11:07:36.4055+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:41.40313+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.10655ms 2023-05-18T11:07:41.4032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:41.40536+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=5.730328ms 2023-05-18T11:07:41.40541+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:46.41342+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.030335ms 2023-05-18T11:07:46.41348+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:46.43279+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=25.867729ms 2023-05-18T11:07:46.43284+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:46.4329+08:00 ERROR [539043,926bb23abb56f86f] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:07:46.46181+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 546995 fields: error="open /proc/546995/status: no such file or directory" 2023-05-18T11:07:51.40555+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=5.781229ms 2023-05-18T11:07:51.40563+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:51.40569+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.404062ms 2023-05-18T11:07:51.40572+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:56.40595+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=5.97853ms 2023-05-18T11:07:56.40601+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:07:56.40611+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.793164ms 2023-05-18T11:07:56.40615+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:01.4057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.01953ms 2023-05-18T11:08:01.40576+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:01.40581+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.732864ms 2023-05-18T11:08:01.40584+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:06.4062+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.478233ms 2023-05-18T11:08:06.40628+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:06.40634+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.260766ms 2023-05-18T11:08:06.40637+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:11.40667+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=5.986581ms 2023-05-18T11:08:11.40673+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:11.40681+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.863973ms 2023-05-18T11:08:11.40685+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:16.36317+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields:, module=monitor.ob, duration="21.7µs" 2023-05-18T11:08:16.36324+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields: module=monitor.ob, eventType=add, duration="10.5µs" 2023-05-18T11:08:16.36327+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields:, module=monitor.ob, duration="4.6µs" 2023-05-18T11:08:16.36334+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields: module=monitor.ob, eventType=add, duration="4.9µs" 2023-05-18T11:08:16.36337+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T11:08:16.37056+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc0006be960 0xc0006bea00 0xc0006beaa0 0xc0006beb40 0xc0006bebe0 0xc0006bec80 0xc0006bed20 0xc0006bedc0 0xc0006bee60 0xc0006bef00 0xc0006befa0 0xc0006bf040 0xc0006bf0e0 0xc0006bf180 0xc0006bf220 0xc0006bf2c0 0xc0006bf360 0xc0006bf400 0xc0006bf4a0 0xc0006bf540 0xc0006bf5e0 0xc0006bf680 0xc0006bf720 0xc0006bf7c0 0xc0006bf860 0xc0006bf900 0xc0006bf9a0 0xc0006bfa40 0xc0006bfae0 0xc0006bfb80 0xc0006bfc20] CollectInterval:1s TimeAlign:false} 2023-05-18T11:08:16.37298+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T11:08:16.37302+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields: input=mysqlTableInput, duration="4.5µs" 2023-05-18T11:08:16.37304+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields:, input=mysqlTableInput, duration="24.8µs" 2023-05-18T11:08:16.37306+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields:, module=monitor.ob, eventType=add, error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)", duration=9.730131ms 2023-05-18T11:08:16.37308+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields: module=monitor.ob, eventType=add, duration=9.752232ms 2023-05-18T11:08:16.37311+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields:, module=monitor.ob, duration=9.844833ms 2023-05-18T11:08:16.37312+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields:, module=monitor.ob, eventType=add, duration=9.893433ms 2023-05-18T11:08:16.37314+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields: module=monitor.ob, duration=9.985734ms 2023-05-18T11:08:16.37317+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 3 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T11:08:16.40051+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.802892ms 2023-05-18T11:08:16.40056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:16.40244+08:00 ERROR [539043,0a7e02a9c2a54f11] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:08:16.40622+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.190884ms 2023-05-18T11:08:16.40626+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:21.40748+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.030195ms 2023-05-18T11:08:21.40755+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:21.40763+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.710785ms 2023-05-18T11:08:21.40767+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:26.40796+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.344785ms 2023-05-18T11:08:26.40802+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:26.40808+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.994903ms 2023-05-18T11:08:26.40811+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:31.40617+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=5.749278ms 2023-05-18T11:08:31.40623+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:31.40632+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.434467ms 2023-05-18T11:08:31.40635+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:36.40607+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=5.735178ms 2023-05-18T11:08:36.40614+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:36.40622+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.244866ms 2023-05-18T11:08:36.40625+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:41.40648+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.192984ms 2023-05-18T11:08:41.40654+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:41.40662+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.532283ms 2023-05-18T11:08:41.40665+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:46.41421+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.772491ms 2023-05-18T11:08:46.41428+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:46.42032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=5.96158ms 2023-05-18T11:08:46.42037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:46.45669+08:00 ERROR [539043,547726aaeea50a3c] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:08:46.47269+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 549681 fields: error="open /proc/549681/status: no such file or directory" 2023-05-18T11:08:51.40627+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=5.95608ms 2023-05-18T11:08:51.40634+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:51.40642+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.081977ms 2023-05-18T11:08:51.40645+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:56.40649+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.818892ms 2023-05-18T11:08:56.40655+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:08:56.40661+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.526683ms 2023-05-18T11:08:56.40665+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:09:01.4062+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.163283ms 2023-05-18T11:09:01.40626+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:09:01.40632+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.253479ms 2023-05-18T11:09:01.40635+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:09:06.40603+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.034881ms 2023-05-18T11:09:06.40611+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:09:06.40616+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.087577ms 2023-05-18T11:09:06.40619+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:09:11.40829+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.604102ms 2023-05-18T11:09:11.40836+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:09:11.40846+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.342807ms 2023-05-18T11:09:11.4085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:09:16.40612+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.601136ms 2023-05-18T11:09:16.40618+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:09:16.40623+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.096414ms 2023-05-18T11:09:16.40626+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:09:16.40732+08:00 ERROR [539043,164bf2799035f998] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:09:21.40669+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.356319ms 2023-05-18T11:09:21.40676+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:09:21.40682+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.703857ms 2023-05-18T11:09:21.40686+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:09:26.40633+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.081114ms 2023-05-18T11:09:26.40639+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:09:26.40647+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.175147ms 2023-05-18T11:09:26.4065+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:09:31.40579+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=5.675806ms 2023-05-18T11:09:31.40585+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:09:31.40595+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.609836ms 2023-05-18T11:09:31.40598+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:09:36.40615+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=6.069414ms 2023-05-18T11:09:36.40621+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:09:36.40628+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.993244ms 2023-05-18T11:09:36.40631+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:09:41.40669+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=6.023913ms 2023-05-18T11:09:41.40675+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:09:41.40681+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.955643ms 2023-05-18T11:09:41.40684+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:09:46.4224+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=26.085889ms 2023-05-18T11:09:46.42247+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:09:46.44741+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=25.491278ms 2023-05-18T11:09:46.44747+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: sudo: 未知用户：admin sudo: 无法初始化策略插件 2023-05-18T11:09:46.45669+08:00 ERROR [539043,3bb91f2c86aafbe0] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:09:51.4108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.854316ms 2023-05-18T11:09:51.41087+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:09:51.41655+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.266455ms 2023-05-18T11:09:51.41661+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:09:56.40969+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.695344ms 2023-05-18T11:09:56.40975+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:09:56.40983+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.754214ms 2023-05-18T11:09:56.40986+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:01.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.986549ms 2023-05-18T11:10:01.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:01.41054+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.017319ms 2023-05-18T11:10:01.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:06.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.664744ms 2023-05-18T11:10:06.4104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:06.41047+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.545711ms 2023-05-18T11:10:06.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:11.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.775246ms 2023-05-18T11:10:11.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:11.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.433308ms 2023-05-18T11:10:11.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:16.40249+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.866166ms 2023-05-18T11:10:16.40254+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:16.41038+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.787646ms 2023-05-18T11:10:16.41043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:16.41152+08:00 ERROR [539043,71bfb818ff6012ee] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:10:21.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.756825ms 2023-05-18T11:10:21.41023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:21.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.731601ms 2023-05-18T11:10:21.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:26.40926+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.564417ms 2023-05-18T11:10:26.40932+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:26.40939+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.180378ms 2023-05-18T11:10:26.40942+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:31.40232+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.461354ms 2023-05-18T11:10:31.40238+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:31.40877+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.269747ms 2023-05-18T11:10:31.40882+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:36.40988+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.978734ms 2023-05-18T11:10:36.40994+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:36.41001+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.768503ms 2023-05-18T11:10:36.41004+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:41.40979+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.615419ms 2023-05-18T11:10:41.40985+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:41.40992+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.458089ms 2023-05-18T11:10:41.40995+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:46.4159+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.621261ms 2023-05-18T11:10:46.41596+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:46.42362+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.521715ms 2023-05-18T11:10:46.42366+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:46.45157+08:00 ERROR [539043,3df9a801e164c2de] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:10:51.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.62992ms 2023-05-18T11:10:51.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:51.41055+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.535093ms 2023-05-18T11:10:51.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:56.40963+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.794427ms 2023-05-18T11:10:56.40975+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:10:56.40983+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.683999ms 2023-05-18T11:10:56.40986+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:01.41225+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.266246ms 2023-05-18T11:11:01.41233+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:01.41269+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.016197ms 2023-05-18T11:11:01.41274+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:06.40985+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.563916ms 2023-05-18T11:11:06.40992+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:06.40999+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.309383ms 2023-05-18T11:11:06.41002+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:11.41004+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.066338ms 2023-05-18T11:11:11.4101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:11.41019+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.909109ms 2023-05-18T11:11:11.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:16.40239+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.926974ms 2023-05-18T11:11:16.40246+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:16.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.922732ms 2023-05-18T11:11:16.41046+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:16.41116+08:00 ERROR [539043,d7ce14bf4edae110] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:11:21.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.962033ms 2023-05-18T11:11:21.41076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:21.41083+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.815605ms 2023-05-18T11:11:21.41086+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:26.4058+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.301153ms 2023-05-18T11:11:26.40586+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:26.40983+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.818161ms 2023-05-18T11:11:26.40988+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:31.41024+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.819661ms 2023-05-18T11:11:31.41031+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:31.41038+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.527241ms 2023-05-18T11:11:31.41041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:36.41326+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.946111ms 2023-05-18T11:11:36.41333+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:36.41351+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.467636ms 2023-05-18T11:11:36.41355+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:41.41082+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.310171ms 2023-05-18T11:11:41.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:41.41096+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.308557ms 2023-05-18T11:11:41.41099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:46.41532+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.837682ms 2023-05-18T11:11:46.4154+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:46.4238+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.299671ms 2023-05-18T11:11:46.42386+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:46.45681+08:00 ERROR [539043,2b36af5ad91eed67] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:11:51.4108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.179969ms 2023-05-18T11:11:51.41087+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:51.41094+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.241256ms 2023-05-18T11:11:51.41097+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:56.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.74866ms 2023-05-18T11:11:56.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:11:56.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.798146ms 2023-05-18T11:11:56.41043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:01.40589+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.990247ms 2023-05-18T11:12:01.40596+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:01.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.216469ms 2023-05-18T11:12:01.41103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:06.40949+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.608457ms 2023-05-18T11:12:06.40955+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:06.40964+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.47474ms 2023-05-18T11:12:06.40971+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:11.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.068367ms 2023-05-18T11:12:11.41041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:11.41048+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.02085ms 2023-05-18T11:12:11.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:16.37359+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields: module=monitor.ob, duration="28.9µs" 2023-05-18T11:12:16.37366+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields: module=monitor.ob, eventType=add, duration="5.001µs" 2023-05-18T11:12:16.37368+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields: module=monitor.ob, duration="4.6µs" 2023-05-18T11:12:16.37372+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields: module=monitor.ob, eventType=add, duration="5.5µs" 2023-05-18T11:12:16.37375+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T11:12:16.37737+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc0002886e0 0xc000288780 0xc000288820 0xc0002888c0 0xc000288960 0xc000288a00 0xc000288aa0 0xc000288b40 0xc000288be0 0xc000288c80 0xc000288d20 0xc000288dc0 0xc000288e60 0xc000288f00 0xc000288fa0 0xc000289040 0xc0002890e0 0xc000289180 0xc000289220 0xc0002892c0 0xc000289360 0xc000289400 0xc0002894a0 0xc000289540 0xc0002895e0 0xc000289680 0xc000289720 0xc0002897c0 0xc000289860 0xc000289900 0xc0002899a0] CollectInterval:1s TimeAlign:false} 2023-05-18T11:12:16.37815+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T11:12:16.37818+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields: input=mysqlTableInput, duration="4.9µs" 2023-05-18T11:12:16.3782+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields:, input=mysqlTableInput, duration="24.9µs" 2023-05-18T11:12:16.37823+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields: eventType=add, error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)", duration=4.514993ms, module=monitor.ob 2023-05-18T11:12:16.37825+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields: duration=4.535693ms, module=monitor.ob, eventType=add 2023-05-18T11:12:16.37827+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields: module=monitor.ob, duration=4.597095ms 2023-05-18T11:12:16.37829+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields:, module=monitor.ob, eventType=add, duration=4.635796ms 2023-05-18T11:12:16.3783+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields: duration=4.739097ms, module=monitor.ob 2023-05-18T11:12:16.37832+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 4 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T11:12:16.40256+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.74708ms 2023-05-18T11:12:16.40264+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:16.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.059766ms 2023-05-18T11:12:16.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:16.41187+08:00 ERROR [539043,401db3ba37b5c5ef] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:12:21.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.25117ms 2023-05-18T11:12:21.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:21.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.037751ms 2023-05-18T11:12:21.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:26.40965+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.701558ms 2023-05-18T11:12:26.40971+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:26.40979+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.49044ms 2023-05-18T11:12:26.40982+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:31.41036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.179234ms 2023-05-18T11:12:31.41043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:31.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.282283ms 2023-05-18T11:12:31.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:36.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.179233ms 2023-05-18T11:12:36.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:36.4108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.15368ms 2023-05-18T11:12:36.41083+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:41.41003+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.733526ms 2023-05-18T11:12:41.41009+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:41.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.941277ms 2023-05-18T11:12:41.4102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:46.41509+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.60124ms 2023-05-18T11:12:46.41516+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:46.42391+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.675442ms 2023-05-18T11:12:46.42396+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:46.4516+08:00 ERROR [539043,7a6c8133f60adb0b] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:12:51.40201+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.756343ms 2023-05-18T11:12:51.40207+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:51.408+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.081632ms 2023-05-18T11:12:51.40805+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:56.40464+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.786176ms 2023-05-18T11:12:56.4047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:12:56.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.941929ms 2023-05-18T11:12:56.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:01.40664+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.166615ms 2023-05-18T11:13:01.40671+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:01.41029+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.073032ms 2023-05-18T11:13:01.41033+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:06.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.152633ms 2023-05-18T11:13:06.41048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:06.41055+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.117379ms 2023-05-18T11:13:06.41059+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:11.40996+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.683126ms 2023-05-18T11:13:11.41003+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:11.41011+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.327667ms 2023-05-18T11:13:11.41014+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:16.40199+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.57524ms 2023-05-18T11:13:16.40207+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:16.40977+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.667925ms 2023-05-18T11:13:16.40982+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:16.41047+08:00 ERROR [539043,651873085c0ba64e] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:13:21.41026+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.629424ms 2023-05-18T11:13:21.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:21.41039+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.457069ms 2023-05-18T11:13:21.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:26.4099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.586824ms 2023-05-18T11:13:26.40997+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:26.41004+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.403768ms 2023-05-18T11:13:26.41007+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:31.41036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.91913ms 2023-05-18T11:13:31.41043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:31.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.790275ms 2023-05-18T11:13:31.41052+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:36.41064+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.096812ms 2023-05-18T11:13:36.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:36.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.635844ms 2023-05-18T11:13:36.41082+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:41.41007+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.679706ms 2023-05-18T11:13:41.41015+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:41.41025+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.593129ms 2023-05-18T11:13:41.41028+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:46.41636+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.828422ms 2023-05-18T11:13:46.41642+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:46.42399+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.494504ms 2023-05-18T11:13:46.42403+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:46.45152+08:00 ERROR [539043,a59fbf684137e97b] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:13:46.4762+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 571256 fields:, error="open /proc/571256/status: no such file or directory" 2023-05-18T11:13:46.47626+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 571273 fields:, error="open /proc/571273/status: no such file or directory" 2023-05-18T11:13:51.40998+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.98131ms 2023-05-18T11:13:51.41004+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:51.4101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.035636ms 2023-05-18T11:13:51.41015+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:56.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.700607ms 2023-05-18T11:13:56.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:13:56.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.585529ms 2023-05-18T11:13:56.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:01.40975+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.857509ms 2023-05-18T11:14:01.40982+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:01.40988+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.786732ms 2023-05-18T11:14:01.40991+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:06.40163+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.652319ms 2023-05-18T11:14:06.40169+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:06.40908+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.485218ms 2023-05-18T11:14:06.40915+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:11.40915+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.705207ms 2023-05-18T11:14:11.40923+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:11.4093+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.218324ms 2023-05-18T11:14:11.40933+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:16.40176+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.737021ms 2023-05-18T11:14:16.40182+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:16.4094+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.511303ms 2023-05-18T11:14:16.40945+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:16.41014+08:00 ERROR [539043,add066ac58109c30] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:14:21.40987+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.206913ms 2023-05-18T11:14:21.40993+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:21.41+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.844233ms 2023-05-18T11:14:21.41003+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:26.40994+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.923009ms 2023-05-18T11:14:26.41+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:26.41005+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.964335ms 2023-05-18T11:14:26.41008+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:31.40994+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.851209ms 2023-05-18T11:14:31.41+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:31.41008+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.988335ms 2023-05-18T11:14:31.41011+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:36.41048+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.863608ms 2023-05-18T11:14:36.41055+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:36.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.754731ms 2023-05-18T11:14:36.41068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:41.41001+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.966451ms 2023-05-18T11:14:41.41009+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:41.41016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.746817ms 2023-05-18T11:14:41.41019+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:46.43235+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.06979ms 2023-05-18T11:14:46.43241+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:46.43248+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.681602ms 2023-05-18T11:14:46.43251+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:46.44892+08:00 ERROR [539043,473a3aa5dedc75fc] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:14:51.40964+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.674145ms 2023-05-18T11:14:51.40972+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:51.40977+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.688415ms 2023-05-18T11:14:51.4098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:56.41102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.94795ms 2023-05-18T11:14:56.4111+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:14:56.41122+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.752836ms 2023-05-18T11:14:56.41125+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:01.41148+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.354058ms 2023-05-18T11:15:01.41155+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:01.41161+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.52595ms 2023-05-18T11:15:01.41165+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:06.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.127253ms 2023-05-18T11:15:06.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:06.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.92532ms 2023-05-18T11:15:06.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:11.40151+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.532461ms 2023-05-18T11:15:11.4016+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:11.40754+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.978351ms 2023-05-18T11:15:11.40761+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:16.40241+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.880768ms 2023-05-18T11:15:16.40247+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:16.41231+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.804786ms 2023-05-18T11:15:16.41236+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:16.41314+08:00 ERROR [539043,56c52d18142ddc1f] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:15:21.40962+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.96825ms 2023-05-18T11:15:21.40969+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:21.40976+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.682816ms 2023-05-18T11:15:21.40979+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:26.41038+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.90775ms 2023-05-18T11:15:26.41044+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:26.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.871318ms 2023-05-18T11:15:26.41055+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:31.40921+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.725446ms 2023-05-18T11:15:31.40929+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:31.40935+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.266608ms 2023-05-18T11:15:31.40938+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:36.40508+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.371515ms 2023-05-18T11:15:36.40514+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:36.41293+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.760847ms 2023-05-18T11:15:36.41298+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:41.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.096653ms 2023-05-18T11:15:41.41054+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:41.41062+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.700915ms 2023-05-18T11:15:41.41066+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:46.40877+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.017462ms 2023-05-18T11:15:46.40883+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:46.41674+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.855415ms 2023-05-18T11:15:46.41679+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:46.44769+08:00 ERROR [539043,7d892529f9dd3b96] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:15:51.40955+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.780314ms 2023-05-18T11:15:51.40963+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:51.4097+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.35054ms 2023-05-18T11:15:51.40974+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:56.40921+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.673313ms 2023-05-18T11:15:56.4093+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:15:56.40935+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.283539ms 2023-05-18T11:15:56.40938+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:01.40516+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.342567ms 2023-05-18T11:16:01.40522+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:01.4132+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.939217ms 2023-05-18T11:16:01.41324+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:06.40252+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.886431ms 2023-05-18T11:16:06.40264+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:06.40838+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.103219ms 2023-05-18T11:16:06.40843+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:11.41048+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.298822ms 2023-05-18T11:16:11.41054+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:11.41065+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.275853ms 2023-05-18T11:16:11.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:16.40217+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.645427ms 2023-05-18T11:16:16.40223+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:16.41022+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.957517ms 2023-05-18T11:16:16.41028+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:16.41094+08:00 ERROR [539043,a5dea72e899cbf9a] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:16:21.41038+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.706013ms 2023-05-18T11:16:21.41044+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:21.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.649245ms 2023-05-18T11:16:21.41055+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:26.41009+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.652712ms 2023-05-18T11:16:26.41016+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:26.41023+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.33154ms 2023-05-18T11:16:26.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:31.40985+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.783914ms 2023-05-18T11:16:31.40995+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:31.41007+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.547143ms 2023-05-18T11:16:31.4101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:36.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.13562ms 2023-05-18T11:16:36.41029+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:36.41039+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.101751ms 2023-05-18T11:16:36.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:41.40936+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.559111ms 2023-05-18T11:16:41.40942+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:41.40947+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.40754ms 2023-05-18T11:16:41.4095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:46.41626+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.788929ms 2023-05-18T11:16:46.41634+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:46.42428+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.873615ms 2023-05-18T11:16:46.42433+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:46.4479+08:00 ERROR [539043,f2f621dffbd41ac1] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:16:51.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.008006ms 2023-05-18T11:16:51.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:51.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.676221ms 2023-05-18T11:16:51.41048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:56.41013+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.803603ms 2023-05-18T11:16:56.41019+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:16:56.41029+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.737521ms 2023-05-18T11:16:56.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:01.4096+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.572001ms 2023-05-18T11:17:01.40966+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:01.40973+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.279515ms 2023-05-18T11:17:01.40976+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:06.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.610901ms 2023-05-18T11:17:06.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:06.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.58812ms 2023-05-18T11:17:06.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:11.41123+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.914418ms 2023-05-18T11:17:11.4113+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:11.41138+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.896137ms 2023-05-18T11:17:11.41141+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:16.40282+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.821317ms 2023-05-18T11:17:16.40289+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:16.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.650302ms 2023-05-18T11:17:16.41065+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:16.41176+08:00 ERROR [539043,4b55ec90fdd73411] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:17:21.40731+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.138687ms 2023-05-18T11:17:21.40737+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:21.4111+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.058606ms 2023-05-18T11:17:21.41115+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:26.41295+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.189708ms 2023-05-18T11:17:26.41302+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:26.41311+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.68816ms 2023-05-18T11:17:26.41314+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:31.41135+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.284409ms 2023-05-18T11:17:31.41142+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:31.4115+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.545232ms 2023-05-18T11:17:31.41153+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:36.40333+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.326823ms 2023-05-18T11:17:36.40339+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:36.40881+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.962705ms 2023-05-18T11:17:36.40886+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:41.40196+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.00662ms 2023-05-18T11:17:41.40202+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:41.40857+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.953305ms 2023-05-18T11:17:41.40864+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:46.43565+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=27.657066ms 2023-05-18T11:17:46.43572+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:46.4358+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=28.283775ms 2023-05-18T11:17:46.43583+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:46.45692+08:00 ERROR [539043,ebe275314b9bdfae] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:17:51.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.028506ms 2023-05-18T11:17:51.41086+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:51.41093+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.951625ms 2023-05-18T11:17:51.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:56.4098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.793603ms 2023-05-18T11:17:56.40986+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:17:56.40993+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.552719ms 2023-05-18T11:17:56.40996+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:01.41007+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.625101ms 2023-05-18T11:18:01.41014+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:01.41022+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.575719ms 2023-05-18T11:18:01.41025+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:06.40266+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.011319ms 2023-05-18T11:18:06.40378+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:06.4083+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.073607ms 2023-05-18T11:18:06.40835+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:11.40403+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.462739ms 2023-05-18T11:18:11.40409+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:11.41004+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.716202ms 2023-05-18T11:18:11.41009+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:16.4022+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.785917ms 2023-05-18T11:18:16.40226+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:16.41051+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.207409ms 2023-05-18T11:18:16.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:16.41133+08:00 ERROR [539043,dc3d143e005d5633] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:18:21.4108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.28901ms 2023-05-18T11:18:21.41088+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:21.41096+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.591333ms 2023-05-18T11:18:21.41099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:26.41106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.228009ms 2023-05-18T11:18:26.41134+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:26.4118+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.979938ms 2023-05-18T11:18:26.41184+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:31.41111+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.28521ms 2023-05-18T11:18:31.41117+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:31.41123+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.322429ms 2023-05-18T11:18:31.41127+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:36.41005+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.979606ms 2023-05-18T11:18:36.41012+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:36.41023+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.711521ms 2023-05-18T11:18:36.41027+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:41.40692+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.768183ms 2023-05-18T11:18:41.407+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:41.40988+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.993706ms 2023-05-18T11:18:41.40993+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:46.40857+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.110621ms 2023-05-18T11:18:46.40864+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:46.41674+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.065507ms 2023-05-18T11:18:46.41678+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:46.45412+08:00 ERROR [539043,1e933803b3db1488] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:18:51.40586+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.10436ms 2023-05-18T11:18:51.40592+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:51.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.113307ms 2023-05-18T11:18:51.41093+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:56.40258+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.494026ms 2023-05-18T11:18:56.40265+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:18:56.40814+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.31161ms 2023-05-18T11:18:56.40819+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:01.41324+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=20.118078ms 2023-05-18T11:19:01.41335+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:01.41456+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.354882ms 2023-05-18T11:19:01.41464+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:06.41081+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.656176ms 2023-05-18T11:19:06.41088+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:06.41093+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.845357ms 2023-05-18T11:19:06.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:11.41038+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.179772ms 2023-05-18T11:19:11.41046+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:11.41055+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.296652ms 2023-05-18T11:19:11.41059+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:16.40295+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.956279ms 2023-05-18T11:19:16.40302+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:16.41187+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.810078ms 2023-05-18T11:19:16.41192+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:16.41262+08:00 ERROR [539043,dc2eeeeb882531f9] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:19:21.40312+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.112589ms 2023-05-18T11:19:21.40319+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:21.41003+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.106971ms 2023-05-18T11:19:21.41008+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:26.40607+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.200507ms 2023-05-18T11:19:26.40614+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:26.41121+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.052171ms 2023-05-18T11:19:26.41127+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:31.41037+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.880969ms 2023-05-18T11:19:31.41044+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:31.41051+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.689347ms 2023-05-18T11:19:31.41055+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:36.41303+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.441992ms 2023-05-18T11:19:36.41309+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:36.41317+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.368571ms 2023-05-18T11:19:36.4132+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:41.40539+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.223608ms 2023-05-18T11:19:41.40545+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:41.40936+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.519767ms 2023-05-18T11:19:41.4094+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:46.41299+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.646647ms 2023-05-18T11:19:46.41305+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:46.42881+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=22.000194ms 2023-05-18T11:19:46.42886+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:46.44788+08:00 ERROR [539043,4575a9bbd4fe3e28] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:19:51.40283+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.810278ms 2023-05-18T11:19:51.4029+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:51.41076+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.822069ms 2023-05-18T11:19:51.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:56.40224+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.735277ms 2023-05-18T11:19:56.4023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:19:56.40884+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.734977ms 2023-05-18T11:19:56.40889+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:01.41144+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.058871ms 2023-05-18T11:20:01.41151+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:01.41161+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.381062ms 2023-05-18T11:20:01.41164+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:06.41004+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.95847ms 2023-05-18T11:20:06.4101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:06.41018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.00105ms 2023-05-18T11:20:06.41021+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:11.40313+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.12209ms 2023-05-18T11:20:11.4032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:11.40968+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.763268ms 2023-05-18T11:20:11.40973+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:16.37941+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields:, module=monitor.ob, duration="25.8µs" 2023-05-18T11:20:16.37948+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields:, module=monitor.ob, eventType=add, duration="6.1µs" 2023-05-18T11:20:16.37951+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields: duration="4.3µs", module=monitor.ob 2023-05-18T11:20:16.37956+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields: eventType=add, duration="4.6µs", module=monitor.ob 2023-05-18T11:20:16.37961+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T11:20:16.38598+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc0005e26e0 0xc0005e2780 0xc0005e2820 0xc0005e28c0 0xc0005e2960 0xc0005e2a00 0xc0005e2aa0 0xc0005e2b40 0xc0005e2be0 0xc0005e2c80 0xc0005e2d20 0xc0005e2dc0 0xc0005e2e60 0xc0005e2f00 0xc0005e2fa0 0xc0005e3040 0xc0005e30e0 0xc0005e3180 0xc0005e3220 0xc0005e32c0 0xc0005e3360 0xc0005e3400 0xc0005e34a0 0xc0005e3540 0xc0005e35e0 0xc0005e3680 0xc0005e3720 0xc0005e37c0 0xc0005e3860 0xc0005e3900 0xc0005e39a0] CollectInterval:1s TimeAlign:false} 2023-05-18T11:20:16.38866+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T11:20:16.38869+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields: duration="4.8µs", input=mysqlTableInput 2023-05-18T11:20:16.38872+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields:, input=mysqlTableInput, duration="27.4µs" 2023-05-18T11:20:16.38874+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields: module=monitor.ob, error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)", duration=9.185481ms, eventType=add 2023-05-18T11:20:16.38876+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields: module=monitor.ob, eventType=add, duration=9.205381ms 2023-05-18T11:20:16.38878+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields: module=monitor.ob, duration=9.272782ms 2023-05-18T11:20:16.3888+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields:, module=monitor.ob, eventType=add, duration=9.317082ms 2023-05-18T11:20:16.38881+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields:, module=monitor.ob, duration=9.423083ms 2023-05-18T11:20:16.38884+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 5 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T11:20:16.40168+08:00 ERROR [539043,87b56d8e46d0a0a6] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:20:16.40191+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.949379ms 2023-05-18T11:20:16.40196+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:16.40844+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.880569ms 2023-05-18T11:20:16.40848+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:21.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.776668ms 2023-05-18T11:20:21.41048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:21.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.812249ms 2023-05-18T11:20:21.4106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:26.4099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.496666ms 2023-05-18T11:20:26.40997+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:26.41006+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.183343ms 2023-05-18T11:20:26.41009+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:31.4097+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.748169ms 2023-05-18T11:20:31.40976+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:31.40984+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.587746ms 2023-05-18T11:20:31.40986+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:36.4049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.024797ms 2023-05-18T11:20:36.40497+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:36.4108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.98177ms 2023-05-18T11:20:36.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:41.40978+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.138342ms 2023-05-18T11:20:41.40985+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:41.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.759669ms 2023-05-18T11:20:41.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:46.41689+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.705738ms 2023-05-18T11:20:46.41695+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:46.43224+08:00 ERROR [539043,ca4ecbca11b0feaf] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:20:46.43238+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=21.965594ms 2023-05-18T11:20:46.43243+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:46.46527+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 616973 fields:, error="open /proc/616973/status: no such file or directory" 2023-05-18T11:20:51.40999+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.533645ms 2023-05-18T11:20:51.41005+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:51.41011+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.898069ms 2023-05-18T11:20:51.41013+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:56.40945+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.857269ms 2023-05-18T11:20:56.40952+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:20:56.4096+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.473445ms 2023-05-18T11:20:56.40963+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:01.41229+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.165472ms 2023-05-18T11:21:01.41235+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:01.41245+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.783766ms 2023-05-18T11:21:01.41248+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:06.40997+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.736969ms 2023-05-18T11:21:06.41006+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:06.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.675647ms 2023-05-18T11:21:06.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:11.41018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.115208ms 2023-05-18T11:21:11.41025+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:11.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.970817ms 2023-05-18T11:21:11.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:16.40376+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.151909ms 2023-05-18T11:21:16.40383+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:16.41214+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.264108ms 2023-05-18T11:21:16.41219+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:16.41294+08:00 ERROR [539043,eb2081ce02107680] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:21:21.40911+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.677416ms 2023-05-18T11:21:21.40918+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:21.40998+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.739007ms 2023-05-18T11:21:21.41003+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:26.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.789508ms 2023-05-18T11:21:26.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:26.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.113517ms 2023-05-18T11:21:26.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:31.41061+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.267608ms 2023-05-18T11:21:31.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:31.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.560917ms 2023-05-18T11:21:31.41082+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:36.4098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.607208ms 2023-05-18T11:21:36.40986+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:36.40992+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.831216ms 2023-05-18T11:21:36.40995+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:41.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.809407ms 2023-05-18T11:21:41.41053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:41.41065+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.779317ms 2023-05-18T11:21:41.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:46.43409+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=27.164226ms 2023-05-18T11:21:46.43415+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:46.43434+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=27.950728ms 2023-05-18T11:21:46.43438+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:46.44752+08:00 ERROR [539043,a72953ed1757876a] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:21:51.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.800908ms 2023-05-18T11:21:51.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:51.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.675716ms 2023-05-18T11:21:51.41053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:56.41007+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.026908ms 2023-05-18T11:21:56.41014+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:21:56.41022+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.132817ms 2023-05-18T11:21:56.41025+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:01.40313+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.14531ms 2023-05-18T11:22:01.4032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:01.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.136008ms 2023-05-18T11:22:01.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:06.41215+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.494508ms 2023-05-18T11:22:06.41221+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:06.41229+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.641119ms 2023-05-18T11:22:06.41231+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:11.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.553409ms 2023-05-18T11:22:11.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:11.41075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.676717ms 2023-05-18T11:22:11.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:16.4021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.996308ms 2023-05-18T11:22:16.40217+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:16.41014+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.924408ms 2023-05-18T11:22:16.41019+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:16.41093+08:00 ERROR [539043,d094a588508242f6] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:22:21.40833+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.656014ms 2023-05-18T11:22:21.4084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:21.4111+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.691908ms 2023-05-18T11:22:21.41116+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:26.40467+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.687512ms 2023-05-18T11:22:26.40474+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:26.41249+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.390009ms 2023-05-18T11:22:26.41254+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:31.40926+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.910608ms 2023-05-18T11:22:31.40933+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:31.40938+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.371916ms 2023-05-18T11:22:31.40941+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:36.40993+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.603608ms 2023-05-18T11:22:36.41+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:36.41007+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.269516ms 2023-05-18T11:22:36.41011+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:41.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.364608ms 2023-05-18T11:22:41.41073+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:41.4108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.360717ms 2023-05-18T11:22:41.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:46.4157+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.240209ms 2023-05-18T11:22:46.41576+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:46.46435+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=27.252326ms 2023-05-18T11:22:46.46441+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:46.46447+08:00 ERROR [539043,5a416715be21824c] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:22:51.41084+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.185508ms 2023-05-18T11:22:51.4109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:51.41097+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.986416ms 2023-05-18T11:22:51.411+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:56.40578+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.562812ms 2023-05-18T11:22:56.40586+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:22:56.40997+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.168708ms 2023-05-18T11:22:56.41003+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:01.4101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.953508ms 2023-05-18T11:23:01.41016+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:01.41024+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.678216ms 2023-05-18T11:23:01.41028+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:06.41007+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.854508ms 2023-05-18T11:23:06.41013+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:06.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.482416ms 2023-05-18T11:23:06.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:11.40948+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.690107ms 2023-05-18T11:23:11.40955+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:11.40966+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.357316ms 2023-05-18T11:23:11.40969+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:16.4029+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.028409ms 2023-05-18T11:23:16.40297+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:16.4109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.890607ms 2023-05-18T11:23:16.41095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:16.41167+08:00 ERROR [539043,5d80821ecd3e62d0] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:23:21.41047+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.009295ms 2023-05-18T11:23:21.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:21.41126+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.78501ms 2023-05-18T11:23:21.41131+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:26.41036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.889693ms 2023-05-18T11:23:26.41044+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:26.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.785198ms 2023-05-18T11:23:26.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:31.40977+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.67049ms 2023-05-18T11:23:31.40983+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:31.40992+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.556796ms 2023-05-18T11:23:31.40995+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:36.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.996894ms 2023-05-18T11:23:36.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:36.41085+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.113602ms 2023-05-18T11:23:36.41088+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:41.40982+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.62739ms 2023-05-18T11:23:41.40988+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:41.40997+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.380493ms 2023-05-18T11:23:41.41+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:46.41657+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.33211ms 2023-05-18T11:23:46.41664+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:46.42436+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.63769ms 2023-05-18T11:23:46.42441+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:46.44462+08:00 ERROR [539043,6cb38d547d14c8a3] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:23:46.4799+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 637366 fields: error="open /proc/637366/status: no such file or directory" 2023-05-18T11:23:46.47996+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 637385 fields: error="open /proc/637385/status: no such file or directory" 2023-05-18T11:23:51.41078+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.969794ms 2023-05-18T11:23:51.41086+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:51.41094+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.087301ms 2023-05-18T11:23:51.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:56.40214+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.160708ms 2023-05-18T11:23:56.4022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:23:56.40764+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.075495ms 2023-05-18T11:23:56.40769+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:01.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.932194ms 2023-05-18T11:24:01.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:01.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.8746ms 2023-05-18T11:24:01.41076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:06.41038+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.083095ms 2023-05-18T11:24:06.41045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:06.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.063101ms 2023-05-18T11:24:06.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:11.41095+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.272898ms 2023-05-18T11:24:11.41101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:11.41112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.087802ms 2023-05-18T11:24:11.41116+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:16.40301+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.054907ms 2023-05-18T11:24:16.40308+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:16.41096+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.849293ms 2023-05-18T11:24:16.41101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:16.41182+08:00 ERROR [539043,e58f54d8323b94bc] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:24:21.40272+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.724803ms 2023-05-18T11:24:21.40278+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:21.40867+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.116896ms 2023-05-18T11:24:21.40872+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:26.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.114395ms 2023-05-18T11:24:26.41083+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:26.41092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.132302ms 2023-05-18T11:24:26.41095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:31.41036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.683791ms 2023-05-18T11:24:31.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:31.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.507395ms 2023-05-18T11:24:31.41053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:36.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.806692ms 2023-05-18T11:24:36.41048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:36.41055+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.741098ms 2023-05-18T11:24:36.4106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:41.41127+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.888905ms 2023-05-18T11:24:41.41134+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:41.41141+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.221415ms 2023-05-18T11:24:41.41144+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:46.41602+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.9851ms 2023-05-18T11:24:46.41608+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:46.43049+08:00 ERROR [539043,05aaebb2952a04a3] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:24:46.43069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=22.703268ms 2023-05-18T11:24:46.43073+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:51.40496+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.770638ms 2023-05-18T11:24:51.40503+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:51.40953+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.484988ms 2023-05-18T11:24:51.40958+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:56.41121+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.261804ms 2023-05-18T11:24:56.41128+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:24:56.41155+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.690603ms 2023-05-18T11:24:56.41163+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:01.4107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.047195ms 2023-05-18T11:25:01.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:01.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.049401ms 2023-05-18T11:25:01.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:06.41234+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.171596ms 2023-05-18T11:25:06.4124+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:06.41249+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.59412ms 2023-05-18T11:25:06.41252+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:11.40317+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.17212ms 2023-05-18T11:25:11.40323+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:11.41041+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.703502ms 2023-05-18T11:25:11.41046+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:16.40235+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.900905ms 2023-05-18T11:25:16.40243+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:16.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.261998ms 2023-05-18T11:25:16.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:16.41143+08:00 ERROR [539043,22b63401e6609d2f] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:25:21.41001+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.842192ms 2023-05-18T11:25:21.41009+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:21.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.784198ms 2023-05-18T11:25:21.41019+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:26.4102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.055995ms 2023-05-18T11:25:26.41027+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:26.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.174703ms 2023-05-18T11:25:26.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:31.40462+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.950836ms 2023-05-18T11:25:31.40468+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:31.41028+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.0162ms 2023-05-18T11:25:31.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:36.40848+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.837885ms 2023-05-18T11:25:36.40854+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:36.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.960999ms 2023-05-18T11:25:36.41048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:41.40973+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.576795ms 2023-05-18T11:25:41.4098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:41.40987+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.276603ms 2023-05-18T11:25:41.4099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:46.43631+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=35.591743ms 2023-05-18T11:25:46.43637+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:46.43642+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=36.207951ms 2023-05-18T11:25:46.43645+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:46.45798+08:00 ERROR [539043,d2f1f9873d66ce19] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:25:51.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.905811ms 2023-05-18T11:25:51.41068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:51.41074+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.111901ms 2023-05-18T11:25:51.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:56.4093+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.525993ms 2023-05-18T11:25:56.40936+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:25:56.4098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.593695ms 2023-05-18T11:25:56.40985+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:01.40997+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.633995ms 2023-05-18T11:26:01.41004+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:01.41015+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.343604ms 2023-05-18T11:26:01.41018+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:06.40985+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.647296ms 2023-05-18T11:26:06.40991+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:06.40998+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.311803ms 2023-05-18T11:26:06.41001+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:11.41291+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.941236ms 2023-05-18T11:26:11.41297+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:11.41306+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.752146ms 2023-05-18T11:26:11.41308+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:16.40377+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.170926ms 2023-05-18T11:26:16.40383+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:16.41148+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.613994ms 2023-05-18T11:26:16.41154+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:16.41217+08:00 ERROR [539043,f2fe27178311ce92] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:26:21.40902+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.361192ms 2023-05-18T11:26:21.4091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:21.41087+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.370705ms 2023-05-18T11:26:21.41092+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:26.41094+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.457805ms 2023-05-18T11:26:26.41101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:26.41113+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.538619ms 2023-05-18T11:26:26.41117+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:31.4099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.710796ms 2023-05-18T11:26:31.40997+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:31.41003+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.554007ms 2023-05-18T11:26:31.41007+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:36.40202+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.046513ms 2023-05-18T11:26:36.40209+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:36.40771+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.136901ms 2023-05-18T11:26:36.40775+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:41.40986+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.599595ms 2023-05-18T11:26:41.40992+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:41.41+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.473506ms 2023-05-18T11:26:41.41003+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:46.43252+08:00 ERROR [539043,73771a8555851ada] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:26:46.43265+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.280728ms 2023-05-18T11:26:46.4327+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:46.43275+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=25.901023ms 2023-05-18T11:26:46.43277+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:51.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.757796ms 2023-05-18T11:26:51.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:51.41089+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.241415ms 2023-05-18T11:26:51.41093+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:56.40474+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.075438ms 2023-05-18T11:26:56.4048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:26:56.40984+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.721396ms 2023-05-18T11:26:56.40989+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:01.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.9726ms 2023-05-18T11:27:01.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:01.41087+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.537919ms 2023-05-18T11:27:01.4109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:06.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.9946ms 2023-05-18T11:27:06.4106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:06.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.404717ms 2023-05-18T11:27:06.41073+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:11.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.400304ms 2023-05-18T11:27:11.41041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:11.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.329116ms 2023-05-18T11:27:11.41053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:16.40153+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.526006ms 2023-05-18T11:27:16.40161+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:16.40957+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.859597ms 2023-05-18T11:27:16.40963+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:16.4103+08:00 ERROR [539043,f66fb02c80ecd099] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:27:21.41107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.360104ms 2023-05-18T11:27:21.41114+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:21.41122+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.319916ms 2023-05-18T11:27:21.41126+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:26.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.973299ms 2023-05-18T11:27:26.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:26.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.85921ms 2023-05-18T11:27:26.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:31.41014+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.729296ms 2023-05-18T11:27:31.4102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:31.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.977111ms 2023-05-18T11:27:31.4103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:36.41179+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.392304ms 2023-05-18T11:27:36.41191+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:36.41203+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.030524ms 2023-05-18T11:27:36.41206+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:41.41023+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.739196ms 2023-05-18T11:27:41.41029+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:41.41039+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.760808ms 2023-05-18T11:27:41.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:46.43451+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.47833ms 2023-05-18T11:27:46.43457+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:46.43468+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=27.126038ms 2023-05-18T11:27:46.43471+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:46.45567+08:00 ERROR [539043,972b73d7185e7987] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:27:51.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.990699ms 2023-05-18T11:27:51.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:51.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.454917ms 2023-05-18T11:27:51.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:56.41028+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.0517ms 2023-05-18T11:27:56.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:27:56.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.126113ms 2023-05-18T11:27:56.41045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:01.40558+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.580945ms 2023-05-18T11:28:01.40565+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:01.41025+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.529994ms 2023-05-18T11:28:01.4103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:06.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.559407ms 2023-05-18T11:28:06.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:06.41051+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.950199ms 2023-05-18T11:28:06.41055+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:11.40943+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.697096ms 2023-05-18T11:28:11.40949+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:11.40957+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.463405ms 2023-05-18T11:28:11.40962+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:16.40157+08:00 ERROR [539043,544bef71cc9567d7] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:28:16.40172+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.739209ms 2023-05-18T11:28:16.40177+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:16.40757+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.975899ms 2023-05-18T11:28:16.40764+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:21.40982+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.806097ms 2023-05-18T11:28:21.40989+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:21.40997+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.681608ms 2023-05-18T11:28:21.41+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:26.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.833297ms 2023-05-18T11:28:26.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:26.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.740409ms 2023-05-18T11:28:26.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:31.40309+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.286216ms 2023-05-18T11:28:31.40316+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:31.40844+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.010799ms 2023-05-18T11:28:31.4085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:36.40955+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.628895ms 2023-05-18T11:28:36.40963+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:36.4097+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.247102ms 2023-05-18T11:28:36.40973+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:41.41342+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.654345ms 2023-05-18T11:28:41.41348+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:41.41355+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.22534ms 2023-05-18T11:28:41.41359+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:46.41334+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.58492ms 2023-05-18T11:28:46.41341+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:46.41386+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.66182ms 2023-05-18T11:28:46.41392+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:46.42963+08:00 ERROR [539043,35385ccdc0575ec1] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:28:51.41005+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.0226ms 2023-05-18T11:28:51.41012+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:51.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.9958ms 2023-05-18T11:28:51.41074+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:56.40982+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.942798ms 2023-05-18T11:28:56.40989+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:28:56.40995+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.87271ms 2023-05-18T11:28:56.40998+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:01.40973+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.757397ms 2023-05-18T11:29:01.40981+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:01.40986+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.86561ms 2023-05-18T11:29:01.4099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:06.41116+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.280304ms 2023-05-18T11:29:06.41123+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:06.4113+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.561618ms 2023-05-18T11:29:06.41134+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:11.41064+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.327304ms 2023-05-18T11:29:11.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:11.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.094213ms 2023-05-18T11:29:11.41081+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:16.40214+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.84391ms 2023-05-18T11:29:16.40221+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:16.4099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.644295ms 2023-05-18T11:29:16.40995+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:16.41073+08:00 ERROR [539043,3db9955e8b6841f7] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:29:21.40182+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.81741ms 2023-05-18T11:29:21.40197+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:21.40771+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.117601ms 2023-05-18T11:29:21.40776+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:26.40583+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.920748ms 2023-05-18T11:29:26.4059+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:26.41388+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.930498ms 2023-05-18T11:29:26.41393+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:31.40323+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.203327ms 2023-05-18T11:29:31.4033+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:31.40989+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.928798ms 2023-05-18T11:29:31.40993+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:36.41005+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.243703ms 2023-05-18T11:29:36.41011+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:36.41016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.097013ms 2023-05-18T11:29:36.41019+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:41.4107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.106501ms 2023-05-18T11:29:41.41076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:41.41085+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.023412ms 2023-05-18T11:29:41.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:46.41888+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.352088ms 2023-05-18T11:29:46.41895+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:46.43433+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=35.793179ms 2023-05-18T11:29:46.4344+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:46.45069+08:00 ERROR [539043,f1d0b2d891cb5ec6] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:29:46.47526+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 678510 fields:, error="open /proc/678510/status: no such file or directory" 2023-05-18T11:29:51.41089+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.019185ms 2023-05-18T11:29:51.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:51.41103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.052881ms 2023-05-18T11:29:51.41106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:56.40998+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.895483ms 2023-05-18T11:29:56.41005+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:29:56.41013+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.745478ms 2023-05-18T11:29:56.41016+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:01.40252+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.760193ms 2023-05-18T11:30:01.40259+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:01.4084+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.351288ms 2023-05-18T11:30:01.40845+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:06.41008+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.701381ms 2023-05-18T11:30:06.41014+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:06.4102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.425374ms 2023-05-18T11:30:06.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:11.41142+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.908183ms 2023-05-18T11:30:11.41149+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:11.4116+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.185792ms 2023-05-18T11:30:11.41164+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:16.38978+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields:, module=monitor.ob, duration="22.601µs" 2023-05-18T11:30:16.38984+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields: module=monitor.ob, eventType=add, duration="6.1µs" 2023-05-18T11:30:16.38987+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields: duration="4.9µs", module=monitor.ob 2023-05-18T11:30:16.38991+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields:, module=monitor.ob, eventType=add, duration="6.5µs" 2023-05-18T11:30:16.38994+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T11:30:16.39371+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc00024a6e0 0xc00024a780 0xc00024a820 0xc00024a8c0 0xc00024a960 0xc00024aa00 0xc00024aaa0 0xc00024ab40 0xc00024abe0 0xc00024ac80 0xc00024ad20 0xc00024adc0 0xc00024ae60 0xc00024af00 0xc00024afa0 0xc00024b040 0xc00024b0e0 0xc00024b180 0xc00024b220 0xc00024b2c0 0xc00024b360 0xc00024b400 0xc00024b4a0 0xc00024b540 0xc00024b5e0 0xc00024b680 0xc00024b720 0xc00024b7c0 0xc00024b860 0xc00024b900 0xc00024b9a0] CollectInterval:1s TimeAlign:false} 2023-05-18T11:30:16.40338+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.491101ms 2023-05-18T11:30:16.40343+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:16.41176+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.282587ms 2023-05-18T11:30:16.41182+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:16.41254+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T11:30:16.41256+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields: input=mysqlTableInput, duration="5.1µs" 2023-05-18T11:30:16.4126+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields: input=mysqlTableInput, duration="44µs" 2023-05-18T11:30:16.41263+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields:, eventType=add, error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)", module=monitor.ob, duration=22.722441ms 2023-05-18T11:30:16.41265+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields:, module=monitor.ob, eventType=add, duration=22.742941ms 2023-05-18T11:30:16.41267+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields: duration=22.801841ms, module=monitor.ob 2023-05-18T11:30:16.41268+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields: duration=22.847142ms, module=monitor.ob, eventType=add 2023-05-18T11:30:16.4127+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields: module=monitor.ob, duration=22.941543ms 2023-05-18T11:30:16.41272+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 6 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T11:30:16.41318+08:00 ERROR [539043,498e2b3cb70d386b] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:30:21.41003+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.061686ms 2023-05-18T11:30:21.4101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:21.41019+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.944879ms 2023-05-18T11:30:21.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:26.41038+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.000285ms 2023-05-18T11:30:26.41044+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:26.41051+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.877279ms 2023-05-18T11:30:26.41054+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:31.41037+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.875184ms 2023-05-18T11:30:31.41045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:31.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.527475ms 2023-05-18T11:30:31.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:36.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.45829ms 2023-05-18T11:30:36.41068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:36.41076+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.378584ms 2023-05-18T11:30:36.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:41.41022+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.235187ms 2023-05-18T11:30:41.41028+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:41.41036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.808878ms 2023-05-18T11:30:41.41041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:46.41523+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.789193ms 2023-05-18T11:30:46.41529+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:46.42355+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.186587ms 2023-05-18T11:30:46.42361+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:46.44671+08:00 ERROR [539043,3b34993bf0b72cac] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:30:51.41041+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.970885ms 2023-05-18T11:30:51.41048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:51.41055+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.812878ms 2023-05-18T11:30:51.4106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:56.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.184986ms 2023-05-18T11:30:56.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:30:56.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.284683ms 2023-05-18T11:30:56.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:01.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.191587ms 2023-05-18T11:31:01.41028+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:01.41036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.940379ms 2023-05-18T11:31:01.4104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:06.40597+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.493232ms 2023-05-18T11:31:06.40603+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:06.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.230287ms 2023-05-18T11:31:06.41059+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:11.40986+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.194086ms 2023-05-18T11:31:11.40996+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:11.41039+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.212982ms 2023-05-18T11:31:11.41045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:16.40202+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.912095ms 2023-05-18T11:31:16.40208+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:16.4097+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.58458ms 2023-05-18T11:31:16.40974+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:16.41038+08:00 ERROR [539043,d7f7238719b80029] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:31:21.40993+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.56098ms 2023-05-18T11:31:21.40999+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:21.41005+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.428473ms 2023-05-18T11:31:21.41008+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:26.41015+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.812383ms 2023-05-18T11:31:26.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:26.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.595676ms 2023-05-18T11:31:26.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:31.40313+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.138707ms 2023-05-18T11:31:31.4032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:31.40932+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.669981ms 2023-05-18T11:31:31.40937+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:36.40219+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.634091ms 2023-05-18T11:31:36.40225+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:36.4081+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.935484ms 2023-05-18T11:31:36.40815+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:41.40778+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=14.560754ms 2023-05-18T11:31:41.40785+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:41.40974+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.617281ms 2023-05-18T11:31:41.4098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:46.4078+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.4457ms 2023-05-18T11:31:46.40786+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:46.41603+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.134386ms 2023-05-18T11:31:46.41607+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:46.45496+08:00 ERROR [539043,01c831c2514827a6] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:31:51.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.661392ms 2023-05-18T11:31:51.41075+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:51.41084+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.574587ms 2023-05-18T11:31:51.41087+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:56.4102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.63838ms 2023-05-18T11:31:56.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:31:56.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.314873ms 2023-05-18T11:31:56.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:01.40162+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.662691ms 2023-05-18T11:32:01.40169+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:01.40891+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.287487ms 2023-05-18T11:32:01.40896+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:06.41092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.297888ms 2023-05-18T11:32:06.41099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:06.41111+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.319083ms 2023-05-18T11:32:06.41114+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:11.41128+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.44529ms 2023-05-18T11:32:11.41134+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:11.41142+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.540286ms 2023-05-18T11:32:11.41145+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:16.40218+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.888594ms 2023-05-18T11:32:16.40224+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:16.40995+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.664681ms 2023-05-18T11:32:16.41001+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:16.41072+08:00 ERROR [539043,fd02dbdef5403b55] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:32:21.41076+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.922583ms 2023-05-18T11:32:21.41082+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:21.41089+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.895179ms 2023-05-18T11:32:21.41092+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:26.40992+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.393373ms 2023-05-18T11:32:26.40999+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:26.41014+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.841283ms 2023-05-18T11:32:26.41018+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:31.41025+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.225687ms 2023-05-18T11:32:31.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:31.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.102181ms 2023-05-18T11:32:31.41043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:36.40987+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.013285ms 2023-05-18T11:32:36.40993+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:36.40999+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.854878ms 2023-05-18T11:32:36.41002+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:41.40922+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.135271ms 2023-05-18T11:32:41.40928+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:41.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.652792ms 2023-05-18T11:32:41.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:46.41344+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.986669ms 2023-05-18T11:32:46.4135+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:46.42911+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.103171ms 2023-05-18T11:32:46.42916+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:46.46357+08:00 ERROR [539043,3f06f4a9db25a3e4] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:32:51.40604+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.574522ms 2023-05-18T11:32:51.4061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:51.41412+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.970985ms 2023-05-18T11:32:51.41416+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:56.41059+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.880283ms 2023-05-18T11:32:56.41065+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:32:56.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.317883ms 2023-05-18T11:32:56.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:01.41+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.803182ms 2023-05-18T11:33:01.41007+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:01.41014+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.01008ms 2023-05-18T11:33:01.41018+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:06.41051+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.969984ms 2023-05-18T11:33:06.41059+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:06.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.945879ms 2023-05-18T11:33:06.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:11.41037+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.191787ms 2023-05-18T11:33:11.41043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:11.41051+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.263783ms 2023-05-18T11:33:11.41054+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:16.40197+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.787793ms 2023-05-18T11:33:16.40204+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:16.40965+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.577981ms 2023-05-18T11:33:16.4097+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:16.41038+08:00 ERROR [539043,d39947c20cdc1e42] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:33:21.41386+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=20.170514ms 2023-05-18T11:33:21.41392+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:21.414+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.499022ms 2023-05-18T11:33:21.41403+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:26.41251+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.169408ms 2023-05-18T11:33:26.4126+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:26.4127+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.381205ms 2023-05-18T11:33:26.41273+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:31.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.904584ms 2023-05-18T11:33:31.4104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:31.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.152581ms 2023-05-18T11:33:31.41053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:36.41092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.164287ms 2023-05-18T11:33:36.41099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:36.41106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.156282ms 2023-05-18T11:33:36.41109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:41.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.042085ms 2023-05-18T11:33:41.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:41.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.93588ms 2023-05-18T11:33:41.41063+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:46.40723+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.139897ms 2023-05-18T11:33:46.40729+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:46.41562+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.291388ms 2023-05-18T11:33:46.41567+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:46.44424+08:00 ERROR [539043,5f923bb6b8cfb4ae] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:33:46.47954+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 705864 fields: error="open /proc/705864/status: no such file or directory" 2023-05-18T11:33:51.40961+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.337973ms 2023-05-18T11:33:51.40967+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:51.40972+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.821483ms 2023-05-18T11:33:51.40975+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:56.40981+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.512079ms 2023-05-18T11:33:56.40988+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:33:56.40997+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.414974ms 2023-05-18T11:33:56.41+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:01.40979+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.653781ms 2023-05-18T11:34:01.40986+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:01.40993+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.703077ms 2023-05-18T11:34:01.40996+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:06.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.915389ms 2023-05-18T11:34:06.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:06.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.930391ms 2023-05-18T11:34:06.41063+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:11.4108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.392595ms 2023-05-18T11:34:11.41086+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:11.41094+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.158693ms 2023-05-18T11:34:11.41098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:16.40247+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.757299ms 2023-05-18T11:34:16.40253+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:16.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.770088ms 2023-05-18T11:34:16.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:16.4111+08:00 ERROR [539043,19ca2cc20cdb73d2] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:34:21.40983+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.628787ms 2023-05-18T11:34:21.4099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:21.41+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.216683ms 2023-05-18T11:34:21.41003+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:26.41322+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.958725ms 2023-05-18T11:34:26.4133+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:26.41355+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.48383ms 2023-05-18T11:34:26.41368+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:31.41012+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.02439ms 2023-05-18T11:34:31.41019+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:31.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.017192ms 2023-05-18T11:34:31.4103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:36.41078+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.401395ms 2023-05-18T11:34:36.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:36.41092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.037093ms 2023-05-18T11:34:36.41095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:41.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.846789ms 2023-05-18T11:34:41.4106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:41.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.945491ms 2023-05-18T11:34:41.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:46.43407+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.362298ms 2023-05-18T11:34:46.43413+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:46.43425+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=26.076195ms 2023-05-18T11:34:46.43428+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:46.45569+08:00 ERROR [539043,2971af9d2c04f893] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:34:51.41102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.072791ms 2023-05-18T11:34:51.4111+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:51.41118+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.252395ms 2023-05-18T11:34:51.41121+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:56.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.060791ms 2023-05-18T11:34:56.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:34:56.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.907591ms 2023-05-18T11:34:56.41093+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:01.40663+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.933446ms 2023-05-18T11:35:01.40671+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:01.41074+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.413195ms 2023-05-18T11:35:01.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:06.40962+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.93209ms 2023-05-18T11:35:06.40968+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:06.40976+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.545186ms 2023-05-18T11:35:06.40979+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:11.41083+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.527196ms 2023-05-18T11:35:11.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:11.411+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.788901ms 2023-05-18T11:35:11.41104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:16.4054+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.368828ms 2023-05-18T11:35:16.40547+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:16.41398+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.470796ms 2023-05-18T11:35:16.41404+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:16.41476+08:00 ERROR [539043,545bd1b31df39b06] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:35:21.4109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.508796ms 2023-05-18T11:35:21.41098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:21.41107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.7768ms 2023-05-18T11:35:21.41112+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:26.41015+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.421695ms 2023-05-18T11:35:26.41021+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:26.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.177494ms 2023-05-18T11:35:26.41033+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:31.40171+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.747699ms 2023-05-18T11:35:31.40177+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:31.4088+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.187492ms 2023-05-18T11:35:31.40884+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:36.41051+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.035391ms 2023-05-18T11:35:36.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:36.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.437797ms 2023-05-18T11:35:36.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:41.41029+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.986291ms 2023-05-18T11:35:41.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:41.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.779789ms 2023-05-18T11:35:41.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:46.41341+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.746199ms 2023-05-18T11:35:46.41348+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:46.42147+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.919589ms 2023-05-18T11:35:46.42153+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:46.44783+08:00 ERROR [539043,5305e26021d96ec0] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:35:51.41126+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.543996ms 2023-05-18T11:35:51.41132+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:51.4114+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.497298ms 2023-05-18T11:35:51.41143+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:56.4097+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.832779ms 2023-05-18T11:35:56.40979+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:35:56.41074+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.168593ms 2023-05-18T11:35:56.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:01.40976+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.883289ms 2023-05-18T11:36:01.40983+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:01.41018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.013592ms 2023-05-18T11:36:01.41023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:06.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.053691ms 2023-05-18T11:36:06.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:06.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.314395ms 2023-05-18T11:36:06.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:11.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.782388ms 2023-05-18T11:36:11.41041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:11.41048+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.571988ms 2023-05-18T11:36:11.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:16.40178+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.692598ms 2023-05-18T11:36:16.40184+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:16.40947+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.584285ms 2023-05-18T11:36:16.40953+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:16.41018+08:00 ERROR [539043,90e9363530c5a9d5] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:36:21.41002+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.748687ms 2023-05-18T11:36:21.41008+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:21.41015+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.746389ms 2023-05-18T11:36:21.41018+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:26.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.137292ms 2023-05-18T11:36:26.41033+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:26.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.867691ms 2023-05-18T11:36:26.41046+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:31.40326+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.280216ms 2023-05-18T11:36:31.40333+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:31.41023+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.431795ms 2023-05-18T11:36:31.41028+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:36.41022+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.129392ms 2023-05-18T11:36:36.41029+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:36.41037+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.944791ms 2023-05-18T11:36:36.4104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:41.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.030891ms 2023-05-18T11:36:41.41073+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:41.4108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.216494ms 2023-05-18T11:36:41.41083+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:46.43255+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=25.62959ms 2023-05-18T11:36:46.43263+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:46.43268+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=26.300697ms 2023-05-18T11:36:46.43271+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:46.45381+08:00 ERROR [539043,92028355abdbb1a7] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:36:51.40211+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.681298ms 2023-05-18T11:36:51.40218+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:51.40831+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.257094ms 2023-05-18T11:36:51.40838+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:56.41087+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.246893ms 2023-05-18T11:36:56.41094+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:36:56.41101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.026092ms 2023-05-18T11:36:56.41104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:01.41041+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.808588ms 2023-05-18T11:37:01.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:01.41054+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.944791ms 2023-05-18T11:37:01.41059+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:06.41162+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.887589ms 2023-05-18T11:37:06.41168+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:06.41176+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.159005ms 2023-05-18T11:37:06.41179+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:11.40312+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.107914ms 2023-05-18T11:37:11.40318+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:11.40987+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.170492ms 2023-05-18T11:37:11.40993+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:16.4028+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.980702ms 2023-05-18T11:37:16.40286+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:16.411+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.093491ms 2023-05-18T11:37:16.41107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:16.41177+08:00 ERROR [539043,1d0405a4b2707e37] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:37:21.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.859988ms 2023-05-18T11:37:21.41058+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:21.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.680788ms 2023-05-18T11:37:21.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:26.40212+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.676598ms 2023-05-18T11:37:26.40219+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:26.40892+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.080892ms 2023-05-18T11:37:26.40897+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:31.40288+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.887301ms 2023-05-18T11:37:31.40295+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:31.40801+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.142392ms 2023-05-18T11:37:31.40806+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:36.40961+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.677087ms 2023-05-18T11:37:36.40967+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:36.40974+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.354484ms 2023-05-18T11:37:36.40978+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:41.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.742288ms 2023-05-18T11:37:41.41059+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:41.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.925891ms 2023-05-18T11:37:41.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:46.41409+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.069402ms 2023-05-18T11:37:46.41418+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:46.42211+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.864189ms 2023-05-18T11:37:46.42223+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:46.44812+08:00 ERROR [539043,7997ff8f28900540] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:37:51.40434+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.578719ms 2023-05-18T11:37:51.4044+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:51.4102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.888589ms 2023-05-18T11:37:51.41025+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:56.40985+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.790588ms 2023-05-18T11:37:56.40994+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:37:56.41013+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.88879ms 2023-05-18T11:37:56.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:01.40809+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=14.851867ms 2023-05-18T11:38:01.40816+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:01.41022+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.95799ms 2023-05-18T11:38:01.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:06.40994+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.996591ms 2023-05-18T11:38:06.41001+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:06.41011+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.781989ms 2023-05-18T11:38:06.41014+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:11.41018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.644386ms 2023-05-18T11:38:11.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:11.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.626388ms 2023-05-18T11:38:11.41034+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:16.40231+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.919901ms 2023-05-18T11:38:16.40237+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:16.41062+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.198193ms 2023-05-18T11:38:16.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:16.41132+08:00 ERROR [539043,21fe8b8e210e0a03] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:38:21.41061+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.193693ms 2023-05-18T11:38:21.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:21.41075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.093893ms 2023-05-18T11:38:21.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:26.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.013697ms 2023-05-18T11:38:26.41023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:26.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.871003ms 2023-05-18T11:38:26.41034+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:31.40197+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.486903ms 2023-05-18T11:38:31.40204+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:31.40836+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.282899ms 2023-05-18T11:38:31.40843+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:36.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.086597ms 2023-05-18T11:38:36.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:36.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.681601ms 2023-05-18T11:38:36.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:41.40221+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.262712ms 2023-05-18T11:38:41.40227+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:41.40774+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.159299ms 2023-05-18T11:38:41.4078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:46.41297+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.618516ms 2023-05-18T11:38:46.41302+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:46.42102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.932895ms 2023-05-18T11:38:46.42107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:46.46308+08:00 ERROR [539043,94d2a5ad41494caa] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:38:46.48469+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 740140 fields: error="open /proc/740140/status: no such file or directory" 2023-05-18T11:38:51.40844+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.922279ms 2023-05-18T11:38:51.4085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:51.40999+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.971096ms 2023-05-18T11:38:51.41003+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:56.40999+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.033597ms 2023-05-18T11:38:56.41006+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:38:56.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.951104ms 2023-05-18T11:38:56.4102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:01.40281+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.16281ms 2023-05-18T11:39:01.40287+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:01.41162+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.704805ms 2023-05-18T11:39:01.41167+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:06.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.5798ms 2023-05-18T11:39:06.41036+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:06.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.2273ms 2023-05-18T11:39:06.41046+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:11.41023+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.027797ms 2023-05-18T11:39:11.4103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:11.41037+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.864104ms 2023-05-18T11:39:11.4104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:16.40176+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.610404ms 2023-05-18T11:39:16.40182+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:16.40981+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.950796ms 2023-05-18T11:39:16.40985+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:16.41054+08:00 ERROR [539043,863fc4b054f81e29] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:39:21.40416+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.270023ms 2023-05-18T11:39:21.40423+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:21.41059+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.807894ms 2023-05-18T11:39:21.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:26.4031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.082221ms 2023-05-18T11:39:26.40318+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:26.40961+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.179499ms 2023-05-18T11:39:26.40967+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:31.40996+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.645992ms 2023-05-18T11:39:31.41003+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:31.41011+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.491898ms 2023-05-18T11:39:31.41014+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:36.40314+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.118822ms 2023-05-18T11:39:36.4032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:36.4092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.905895ms 2023-05-18T11:39:36.40925+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:41.41007+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.419302ms 2023-05-18T11:39:41.41013+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:41.4102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.032405ms 2023-05-18T11:39:41.41023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:46.42429+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.42591ms 2023-05-18T11:39:46.42436+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:46.42441+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.037617ms 2023-05-18T11:39:46.42444+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:46.43708+08:00 ERROR [539043,b10dd6acc04a1e83] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:39:51.40155+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.580803ms 2023-05-18T11:39:51.40163+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:51.40772+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.121698ms 2023-05-18T11:39:51.40779+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:56.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.2814ms 2023-05-18T11:39:56.41033+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:39:56.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.153407ms 2023-05-18T11:39:56.41043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:01.41037+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.2948ms 2023-05-18T11:40:01.41043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:01.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.39231ms 2023-05-18T11:40:01.41054+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:06.40592+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.450438ms 2023-05-18T11:40:06.40599+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:06.41437+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.3401ms 2023-05-18T11:40:06.41442+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:11.40444+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.78563ms 2023-05-18T11:40:11.4045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:11.41169+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.381101ms 2023-05-18T11:40:11.41174+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:16.40259+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.926508ms 2023-05-18T11:40:16.40266+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:16.4109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.200299ms 2023-05-18T11:40:16.41094+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:16.41164+08:00 ERROR [539043,df8ff7a63f744378] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:40:16.41278+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields: module=monitor.ob, duration="16.2µs" 2023-05-18T11:40:16.41283+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields:, module=monitor.ob, eventType=add, duration="5.4µs" 2023-05-18T11:40:16.41287+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields:, module=monitor.ob, duration="17.501µs" 2023-05-18T11:40:16.41291+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields:, module=monitor.ob, eventType=add, duration="3.9µs" 2023-05-18T11:40:16.41293+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T11:40:16.42044+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc0006a48c0 0xc0006a4960 0xc0006a4a00 0xc0006a4aa0 0xc0006a4b40 0xc0006a4be0 0xc0006a4c80 0xc0006a4d20 0xc0006a4dc0 0xc0006a4e60 0xc0006a4f00 0xc0006a4fa0 0xc0006a5040 0xc0006a50e0 0xc0006a5180 0xc0006a5220 0xc0006a52c0 0xc0006a5360 0xc0006a5400 0xc0006a54a0 0xc0006a5540 0xc0006a55e0 0xc0006a5680 0xc0006a5720 0xc0006a57c0 0xc0006a5860 0xc0006a5900 0xc0006a59a0 0xc0006a5a40 0xc0006a5ae0 0xc0006a5b80] CollectInterval:1s TimeAlign:false} 2023-05-18T11:40:16.42245+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T11:40:16.42248+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields:, input=mysqlTableInput, duration="4.2µs" 2023-05-18T11:40:16.4225+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields:, input=mysqlTableInput, duration="22.501µs" 2023-05-18T11:40:16.42252+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields:, module=monitor.ob, eventType=add, error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)", duration=9.622116ms 2023-05-18T11:40:16.42254+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields:, module=monitor.ob, eventType=add, duration=9.640116ms 2023-05-18T11:40:16.42256+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields: duration=9.708017ms, module=monitor.ob 2023-05-18T11:40:16.42257+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields: duration=9.746117ms, module=monitor.ob, eventType=add 2023-05-18T11:40:16.42263+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields: module=monitor.ob, duration=9.871019ms 2023-05-18T11:40:16.42266+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 7 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T11:40:21.41177+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.148098ms 2023-05-18T11:40:21.41183+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:21.41191+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.522424ms 2023-05-18T11:40:21.41196+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:26.41131+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.528203ms 2023-05-18T11:40:26.41138+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:26.41146+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.076418ms 2023-05-18T11:40:26.41151+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:31.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.057697ms 2023-05-18T11:40:31.41046+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:31.41054+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.821703ms 2023-05-18T11:40:31.41059+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:36.41036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.988596ms 2023-05-18T11:40:36.41043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:36.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.077906ms 2023-05-18T11:40:36.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:41.4101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.439502ms 2023-05-18T11:40:41.41016+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:41.41024+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.096907ms 2023-05-18T11:40:41.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:46.41511+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.661804ms 2023-05-18T11:40:46.41517+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:46.42316+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.930796ms 2023-05-18T11:40:46.42321+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:46.4382+08:00 ERROR [539043,3f3a37fcda882fdd] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:40:51.41105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.3057ms 2023-05-18T11:40:51.41112+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:51.4112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.468411ms 2023-05-18T11:40:51.41123+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:56.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.064197ms 2023-05-18T11:40:56.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:40:56.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.987505ms 2023-05-18T11:40:56.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:01.41009+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.106098ms 2023-05-18T11:41:01.41016+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:01.41025+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.067206ms 2023-05-18T11:41:01.41028+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:06.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.202599ms 2023-05-18T11:41:06.41098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:06.41105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.380509ms 2023-05-18T11:41:06.41109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:11.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.043597ms 2023-05-18T11:41:11.41033+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:11.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.081206ms 2023-05-18T11:41:11.41043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:16.40297+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.17331ms 2023-05-18T11:41:16.40304+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:16.41154+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.459001ms 2023-05-18T11:41:16.4116+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:16.41229+08:00 ERROR [539043,6884c1d37ff855f8] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:41:21.4107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.156898ms 2023-05-18T11:41:21.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:21.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.869903ms 2023-05-18T11:41:21.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:26.40312+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.130323ms 2023-05-18T11:41:26.40319+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:26.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.190499ms 2023-05-18T11:41:26.4104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:31.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.096198ms 2023-05-18T11:41:31.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:31.41062+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.107707ms 2023-05-18T11:41:31.41066+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:36.411+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.782606ms 2023-05-18T11:41:36.41107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:36.41116+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.940616ms 2023-05-18T11:41:36.41119+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:41.40172+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.747706ms 2023-05-18T11:41:41.40179+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:41.40855+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.969796ms 2023-05-18T11:41:41.40862+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:46.42767+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=25.893312ms 2023-05-18T11:41:46.42774+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:46.45362+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.59202ms 2023-05-18T11:41:46.45369+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:46.45374+08:00 ERROR [539043,d886de606808e248] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:41:51.41082+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.118498ms 2023-05-18T11:41:51.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:51.41101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.274208ms 2023-05-18T11:41:51.41104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:56.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.140298ms 2023-05-18T11:41:56.41074+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:41:56.41083+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.049106ms 2023-05-18T11:41:56.41086+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:01.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.222799ms 2023-05-18T11:42:01.41023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:01.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.107306ms 2023-05-18T11:42:01.41034+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:06.4063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.284248ms 2023-05-18T11:42:06.40636+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:06.41099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.055997ms 2023-05-18T11:42:06.41104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:11.41029+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.812195ms 2023-05-18T11:42:11.41036+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:11.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.5991ms 2023-05-18T11:42:11.41046+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:16.40271+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.997209ms 2023-05-18T11:42:16.40277+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:16.41095+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.132698ms 2023-05-18T11:42:16.411+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:16.41179+08:00 ERROR [539043,2fa16c101efe206c] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:42:21.41082+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.271209ms 2023-05-18T11:42:21.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:21.41094+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.468302ms 2023-05-18T11:42:21.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:26.41089+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.046497ms 2023-05-18T11:42:26.41095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:26.41104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.131207ms 2023-05-18T11:42:26.41107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:31.41074+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.888195ms 2023-05-18T11:42:31.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:31.41088+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.930504ms 2023-05-18T11:42:31.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:36.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.220699ms 2023-05-18T11:42:36.41099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:36.41107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.40861ms 2023-05-18T11:42:36.4111+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:41.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.159798ms 2023-05-18T11:42:41.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:41.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.154307ms 2023-05-18T11:42:41.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:46.40849+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.095105ms 2023-05-18T11:42:46.40855+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:46.41654+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.937091ms 2023-05-18T11:42:46.41659+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:46.45591+08:00 ERROR [539043,29bf8f48b62e19c0] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:42:51.41092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.448497ms 2023-05-18T11:42:51.41099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:51.41108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.648303ms 2023-05-18T11:42:51.41111+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:56.41039+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.269495ms 2023-05-18T11:42:56.41045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:42:56.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.016095ms 2023-05-18T11:42:56.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:01.40267+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.812002ms 2023-05-18T11:43:01.40274+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:01.40846+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.926591ms 2023-05-18T11:43:01.40851+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:06.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.299395ms 2023-05-18T11:43:06.41075+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:06.41134+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.764904ms 2023-05-18T11:43:06.41139+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:11.41061+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.293899ms 2023-05-18T11:43:11.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:11.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.419196ms 2023-05-18T11:43:11.41074+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:16.40412+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.116716ms 2023-05-18T11:43:16.40418+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:16.41243+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.127794ms 2023-05-18T11:43:16.41248+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:16.4132+08:00 ERROR [539043,964275d404122c4f] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:43:21.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.526798ms 2023-05-18T11:43:21.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:21.4117+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.457012ms 2023-05-18T11:43:21.41174+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:26.40717+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.533655ms 2023-05-18T11:43:26.40723+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:26.41022+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.86999ms 2023-05-18T11:43:26.41027+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:31.41004+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.724689ms 2023-05-18T11:43:31.4101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:31.41022+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.428489ms 2023-05-18T11:43:31.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:36.40235+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.248106ms 2023-05-18T11:43:36.40242+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:36.41121+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.754801ms 2023-05-18T11:43:36.41126+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:41.41104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.441001ms 2023-05-18T11:43:41.4111+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:41.41119+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.7027ms 2023-05-18T11:43:41.41122+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:46.43745+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.169706ms 2023-05-18T11:43:46.43752+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:46.43807+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.199906ms 2023-05-18T11:43:46.43812+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:46.45473+08:00 ERROR [539043,5b392ab4fba3294f] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:43:51.40231+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.801201ms 2023-05-18T11:43:51.40238+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:51.40835+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.149394ms 2023-05-18T11:43:51.4084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:56.41099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.143093ms 2023-05-18T11:43:56.41106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:43:56.41116+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.157497ms 2023-05-18T11:43:56.41119+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:01.40647+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.822347ms 2023-05-18T11:44:01.40655+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:01.41208+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.256195ms 2023-05-18T11:44:01.41216+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:06.41028+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.024092ms 2023-05-18T11:44:06.41036+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:06.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.343999ms 2023-05-18T11:44:06.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:11.41064+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.492298ms 2023-05-18T11:44:11.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:11.41081+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.538302ms 2023-05-18T11:44:11.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:16.40246+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.824002ms 2023-05-18T11:44:16.40252+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:16.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.755489ms 2023-05-18T11:44:16.41036+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:16.41152+08:00 ERROR [539043,222e41e0a4ee4d03] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:44:21.41028+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.558187ms 2023-05-18T11:44:21.41034+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:21.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.520989ms 2023-05-18T11:44:21.41059+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:26.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.560787ms 2023-05-18T11:44:26.41027+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:26.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.468289ms 2023-05-18T11:44:26.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:31.4101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.981091ms 2023-05-18T11:44:31.41018+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:31.41025+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.125997ms 2023-05-18T11:44:31.41028+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:36.40698+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.483855ms 2023-05-18T11:44:36.40705+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:36.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.068293ms 2023-05-18T11:44:36.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:41.4108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.293196ms 2023-05-18T11:44:41.41087+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:41.41097+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.945994ms 2023-05-18T11:44:41.411+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:46.43264+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=27.086211ms 2023-05-18T11:44:46.4327+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:46.43281+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=27.751719ms 2023-05-18T11:44:46.43283+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:46.45328+08:00 ERROR [539043,585a7f10ca247868] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:44:51.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.79449ms 2023-05-18T11:44:51.41027+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:51.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.3676ms 2023-05-18T11:44:51.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:56.40251+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.575198ms 2023-05-18T11:44:56.40257+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:44:56.40793+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.215094ms 2023-05-18T11:44:56.40798+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:01.41002+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.025895ms 2023-05-18T11:45:01.41008+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:01.41018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.184194ms 2023-05-18T11:45:01.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:06.40867+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.739969ms 2023-05-18T11:45:06.40875+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:06.4108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.586388ms 2023-05-18T11:45:06.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:11.40955+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.664388ms 2023-05-18T11:45:11.40963+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:11.40971+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.55799ms 2023-05-18T11:45:11.40974+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:16.40308+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.224406ms 2023-05-18T11:45:16.40314+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:16.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.683489ms 2023-05-18T11:45:16.4109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:16.41155+08:00 ERROR [539043,91c05964e6174382] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:45:21.41038+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.230395ms 2023-05-18T11:45:21.41046+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:21.41054+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.283099ms 2023-05-18T11:45:21.41058+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:26.40326+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.039816ms 2023-05-18T11:45:26.40332+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:26.40767+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.88489ms 2023-05-18T11:45:26.40772+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:31.41322+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.23992ms 2023-05-18T11:45:31.41328+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:31.41493+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.7169ms 2023-05-18T11:45:31.41498+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:36.40969+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.608888ms 2023-05-18T11:45:36.40976+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:36.40985+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.50779ms 2023-05-18T11:45:36.4099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:41.40981+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.623188ms 2023-05-18T11:45:41.40989+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:41.40997+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.181885ms 2023-05-18T11:45:41.41+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:46.44961+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=25.666594ms 2023-05-18T11:45:46.44968+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:46.44978+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.327502ms 2023-05-18T11:45:46.44981+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:46.4697+08:00 ERROR [539043,3dd5adf61815d646] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:45:51.41039+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.83449ms 2023-05-18T11:45:51.41046+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:51.41055+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.783692ms 2023-05-18T11:45:51.41059+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:56.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.903791ms 2023-05-18T11:45:56.41075+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:45:56.41083+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.173897ms 2023-05-18T11:45:56.41087+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:01.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.794389ms 2023-05-18T11:46:01.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:01.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.955494ms 2023-05-18T11:46:01.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:06.41054+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.211594ms 2023-05-18T11:46:06.41063+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:06.41071+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.077596ms 2023-05-18T11:46:06.41075+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:11.4112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.83029ms 2023-05-18T11:46:11.41126+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:11.41135+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.4535ms 2023-05-18T11:46:11.41139+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:16.40216+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.909502ms 2023-05-18T11:46:16.40223+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:16.41012+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.84519ms 2023-05-18T11:46:16.41018+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:16.41097+08:00 ERROR [539043,b96dff9a20cb5bae] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:46:21.4031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.124217ms 2023-05-18T11:46:21.40316+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:21.40957+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.744689ms 2023-05-18T11:46:21.40973+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:26.41078+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.171297ms 2023-05-18T11:46:26.41086+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:26.41093+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.317295ms 2023-05-18T11:46:26.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:31.41206+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.620911ms 2023-05-18T11:46:31.41214+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:31.41221+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.530512ms 2023-05-18T11:46:31.41224+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:36.4108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.161494ms 2023-05-18T11:46:36.41087+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:36.41095+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.490201ms 2023-05-18T11:46:36.41098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:41.41112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.6987ms 2023-05-18T11:46:41.41119+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:41.41127+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.708503ms 2023-05-18T11:46:41.41131+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:46.4166+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.937403ms 2023-05-18T11:46:46.41667+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:46.42481+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.047392ms 2023-05-18T11:46:46.42486+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:46.45684+08:00 ERROR [539043,6400f072c7e9888b] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:46:51.4102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.123593ms 2023-05-18T11:46:51.41027+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:51.41036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.127997ms 2023-05-18T11:46:51.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:56.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.947292ms 2023-05-18T11:46:56.41036+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:46:56.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.031895ms 2023-05-18T11:46:56.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:01.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.984896ms 2023-05-18T11:47:01.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:01.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.184706ms 2023-05-18T11:47:01.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:06.41165+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.3334ms 2023-05-18T11:47:06.41171+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:06.4118+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.229719ms 2023-05-18T11:47:06.41183+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:11.40528+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.585338ms 2023-05-18T11:47:11.40535+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:11.41345+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.050096ms 2023-05-18T11:47:11.4135+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:16.40221+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.22171ms 2023-05-18T11:47:16.40228+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:16.41062+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.271499ms 2023-05-18T11:47:16.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:16.41133+08:00 ERROR [539043,cd15195c0e2c024a] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:47:21.40984+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.764193ms 2023-05-18T11:47:21.40991+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:21.40998+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.6445ms 2023-05-18T11:47:21.41001+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:26.41133+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.205498ms 2023-05-18T11:47:26.4114+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:26.41147+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.321119ms 2023-05-18T11:47:26.4115+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:31.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.908594ms 2023-05-18T11:47:31.41068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:31.41075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.959903ms 2023-05-18T11:47:31.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:36.41095+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.990496ms 2023-05-18T11:47:36.41101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:36.41111+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.086405ms 2023-05-18T11:47:36.41115+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:41.40561+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.459649ms 2023-05-18T11:47:41.40568+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:41.4144+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.228611ms 2023-05-18T11:47:41.41446+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:46.41667+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.800506ms 2023-05-18T11:47:46.41673+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:46.42434+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.52489ms 2023-05-18T11:47:46.42438+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:46.4568+08:00 ERROR [539043,2d4a9395388d2f26] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:47:51.40186+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.899306ms 2023-05-18T11:47:51.40192+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:51.40826+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.676204ms 2023-05-18T11:47:51.40831+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:56.41061+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.076496ms 2023-05-18T11:47:56.41068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:47:56.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.083204ms 2023-05-18T11:47:56.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:01.40212+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.146009ms 2023-05-18T11:48:01.40218+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:01.40896+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.322799ms 2023-05-18T11:48:01.40901+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:06.40827+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.243671ms 2023-05-18T11:48:06.40834+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:06.41109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.111997ms 2023-05-18T11:48:06.41116+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:11.41018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.835594ms 2023-05-18T11:48:11.41025+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:11.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.807301ms 2023-05-18T11:48:11.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:16.40215+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.15741ms 2023-05-18T11:48:16.40221+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:16.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.051396ms 2023-05-18T11:48:16.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:16.41116+08:00 ERROR [539043,9d79e00e213fcc97] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:48:21.41024+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.647391ms 2023-05-18T11:48:21.41031+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:21.41038+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.6913ms 2023-05-18T11:48:21.41041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:26.41014+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.012495ms 2023-05-18T11:48:26.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:26.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.931702ms 2023-05-18T11:48:26.41033+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:31.40827+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.642376ms 2023-05-18T11:48:31.40833+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:31.40991+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.610591ms 2023-05-18T11:48:31.40996+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:36.4031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.08912ms 2023-05-18T11:48:36.40316+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:36.40941+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.47619ms 2023-05-18T11:48:36.40947+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:41.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.959795ms 2023-05-18T11:48:41.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:41.41047+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.011803ms 2023-05-18T11:48:41.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:46.40971+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.950431ms 2023-05-18T11:48:46.40977+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:46.4181+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.291399ms 2023-05-18T11:48:46.41814+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:46.46036+08:00 ERROR [539043,3cc1a107a11f4e9f] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:48:51.40539+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.215947ms 2023-05-18T11:48:51.40547+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:51.40998+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.154798ms 2023-05-18T11:48:51.41004+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:56.40237+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.997008ms 2023-05-18T11:48:56.40244+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:48:56.40864+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.581703ms 2023-05-18T11:48:56.40869+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:01.40292+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.982907ms 2023-05-18T11:49:01.40298+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:01.40749+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.878994ms 2023-05-18T11:49:01.40753+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:06.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.534598ms 2023-05-18T11:49:06.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:06.41048+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.115797ms 2023-05-18T11:49:06.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:11.40589+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.086945ms 2023-05-18T11:49:11.40596+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:11.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.713192ms 2023-05-18T11:49:11.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:16.40235+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.971907ms 2023-05-18T11:49:16.40241+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:16.41013+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.627191ms 2023-05-18T11:49:16.41017+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:16.4118+08:00 ERROR [539043,d0c03390e42d41ce] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:49:21.41209+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.571722ms 2023-05-18T11:49:21.41216+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:21.42052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.315899ms 2023-05-18T11:49:21.42057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:26.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.282899ms 2023-05-18T11:49:26.41065+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:26.41074+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.136305ms 2023-05-18T11:49:26.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:31.41132+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.942307ms 2023-05-18T11:49:31.41138+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:31.41145+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.280019ms 2023-05-18T11:49:31.41148+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:36.41272+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.700504ms 2023-05-18T11:49:36.4128+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:36.41299+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.541234ms 2023-05-18T11:49:36.41303+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:41.40854+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.442684ms 2023-05-18T11:49:41.40863+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:41.41011+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.033496ms 2023-05-18T11:49:41.41017+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:46.42511+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.58429ms 2023-05-18T11:49:46.42517+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:46.42524+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.6664ms 2023-05-18T11:49:46.42527+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:46.4615+08:00 ERROR [539043,0be6e5ca13dab8fe] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:49:51.40216+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.549902ms 2023-05-18T11:49:51.40222+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:51.41304+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.803453ms 2023-05-18T11:49:51.4131+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:56.41103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.436601ms 2023-05-18T11:49:56.41111+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:49:56.41119+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.230506ms 2023-05-18T11:49:56.41122+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:01.41199+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.613103ms 2023-05-18T11:50:01.41207+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:01.41215+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.106817ms 2023-05-18T11:50:01.41217+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:06.41104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.174005ms 2023-05-18T11:50:06.41113+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:06.4128+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.758316ms 2023-05-18T11:50:06.41287+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:11.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.659592ms 2023-05-18T11:50:11.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:11.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.7184ms 2023-05-18T11:50:11.41076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:16.40191+08:00 ERROR [539043,82c83520c33b0377] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:50:16.40593+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.061944ms 2023-05-18T11:50:16.40599+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:16.40984+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.354312ms 2023-05-18T11:50:16.40989+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:16.42298+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields:, module=monitor.ob, duration="19.4µs" 2023-05-18T11:50:16.42304+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields:, module=monitor.ob, eventType=add, duration="5.4µs" 2023-05-18T11:50:16.42307+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields:, module=monitor.ob, duration="4.7µs" 2023-05-18T11:50:16.42312+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields:, module=monitor.ob, eventType=add, duration="4.4µs" 2023-05-18T11:50:16.42316+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T11:50:16.42693+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc000270640 0xc0002706e0 0xc000270780 0xc000270820 0xc0002708c0 0xc000270960 0xc000270a00 0xc000270aa0 0xc000270b40 0xc000270be0 0xc000270c80 0xc000270d20 0xc000270dc0 0xc000270e60 0xc000270f00 0xc000270fa0 0xc000271040 0xc0002710e0 0xc000271180 0xc000271220 0xc0002712c0 0xc000271360 0xc000271400 0xc0002714a0 0xc000271540 0xc0002715e0 0xc000271680 0xc000271720 0xc0002717c0 0xc000271860 0xc000271900] CollectInterval:1s TimeAlign:false} 2023-05-18T11:50:16.42781+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T11:50:16.42786+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields:, input=mysqlTableInput, duration="4.9µs" 2023-05-18T11:50:16.42788+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields:, input=mysqlTableInput, duration="25.6µs" 2023-05-18T11:50:16.4279+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields: eventType=add, error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)", duration=4.789657ms, module=monitor.ob 2023-05-18T11:50:16.42792+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields: module=monitor.ob, eventType=add, duration=4.809858ms 2023-05-18T11:50:16.42794+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields:, module=monitor.ob, duration=4.879559ms 2023-05-18T11:50:16.42796+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields: module=monitor.ob, eventType=add, duration=4.921459ms 2023-05-18T11:50:16.42797+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields: module=monitor.ob, duration=5.00766ms 2023-05-18T11:50:16.42799+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 8 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T11:50:21.40291+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.239611ms 2023-05-18T11:50:21.40298+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:21.40967+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.366712ms 2023-05-18T11:50:21.40973+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:26.41004+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.024496ms 2023-05-18T11:50:26.41011+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:26.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.7514ms 2023-05-18T11:50:26.4102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:31.41219+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.204098ms 2023-05-18T11:50:31.41225+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:31.41232+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.297119ms 2023-05-18T11:50:31.41235+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:36.40431+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.363936ms 2023-05-18T11:50:36.40438+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:36.41155+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.545514ms 2023-05-18T11:50:36.41161+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:41.4099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.753001ms 2023-05-18T11:50:41.40996+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:41.40999+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.202198ms 2023-05-18T11:50:41.41004+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:46.42704+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=20.667148ms 2023-05-18T11:50:46.42711+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:46.42726+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.136733ms 2023-05-18T11:50:46.42731+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:46.44844+08:00 ERROR [539043,107cfa72dfff5443] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:50:46.47567+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 822136 fields:, error="open /proc/822136/status: no such file or directory" 2023-05-18T11:50:51.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.154797ms 2023-05-18T11:50:51.41046+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:51.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.123405ms 2023-05-18T11:50:51.41058+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:56.40875+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.573586ms 2023-05-18T11:50:56.40881+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:50:56.41007+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.226899ms 2023-05-18T11:50:56.41014+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:01.41005+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.986295ms 2023-05-18T11:51:01.41013+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:01.4102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.108005ms 2023-05-18T11:51:01.41023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:06.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.884594ms 2023-05-18T11:51:06.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:06.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.062104ms 2023-05-18T11:51:06.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:11.4113+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.444301ms 2023-05-18T11:51:11.41139+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:11.41147+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.461309ms 2023-05-18T11:51:11.4115+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:16.40266+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.951008ms 2023-05-18T11:51:16.40273+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:16.41116+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.3917ms 2023-05-18T11:51:16.41122+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:16.41192+08:00 ERROR [539043,59dccc07f5b88aa4] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:51:21.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.064696ms 2023-05-18T11:51:21.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:21.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.936103ms 2023-05-18T11:51:21.41063+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:26.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.097097ms 2023-05-18T11:51:26.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:26.41075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.012804ms 2023-05-18T11:51:26.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:31.40284+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.880219ms 2023-05-18T11:51:31.40292+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:31.40785+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.250099ms 2023-05-18T11:51:31.4079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:36.41175+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.536002ms 2023-05-18T11:51:36.41181+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:36.41194+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.917114ms 2023-05-18T11:51:36.41197+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:41.41036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.3525ms 2023-05-18T11:51:41.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:41.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.287406ms 2023-05-18T11:51:41.41053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:46.42485+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.6582ms 2023-05-18T11:51:46.42492+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:46.42498+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.246506ms 2023-05-18T11:51:46.42503+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:46.45496+08:00 ERROR [539043,3154962e13f66006] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:51:51.40998+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.108797ms 2023-05-18T11:51:51.41005+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:51.41015+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.989803ms 2023-05-18T11:51:51.41018+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:56.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.283199ms 2023-05-18T11:51:56.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:51:56.41071+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.202806ms 2023-05-18T11:51:56.41074+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:01.41323+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.957539ms 2023-05-18T11:52:01.41331+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:01.41421+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.3576ms 2023-05-18T11:52:01.41427+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:06.41+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.002595ms 2023-05-18T11:52:06.41006+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:06.41013+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.784201ms 2023-05-18T11:52:06.41016+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:11.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.190698ms 2023-05-18T11:52:11.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:11.41059+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.136005ms 2023-05-18T11:52:11.41063+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:16.40208+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.086209ms 2023-05-18T11:52:16.40216+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:16.41114+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.910306ms 2023-05-18T11:52:16.41119+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:16.4119+08:00 ERROR [539043,9a2479864a8896ec] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:52:21.4108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.469501ms 2023-05-18T11:52:21.41088+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:21.41096+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.419609ms 2023-05-18T11:52:21.41099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:26.40946+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.106792ms 2023-05-18T11:52:26.40952+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:26.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.191498ms 2023-05-18T11:52:26.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:31.41085+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.969496ms 2023-05-18T11:52:31.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:31.41099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.978903ms 2023-05-18T11:52:31.41102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:36.40314+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.125421ms 2023-05-18T11:52:36.40321+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:36.41+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.893494ms 2023-05-18T11:52:36.41005+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:41.4018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.830506ms 2023-05-18T11:52:41.40186+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:41.40746+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.866894ms 2023-05-18T11:52:41.40751+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:46.41619+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.110197ms 2023-05-18T11:52:46.41626+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:46.41641+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.416832ms 2023-05-18T11:52:46.41644+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:46.44829+08:00 ERROR [539043,ad3da04c92529f48] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:52:51.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.105797ms 2023-05-18T11:52:51.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:51.41085+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.902602ms 2023-05-18T11:52:51.41088+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:56.41025+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.979396ms 2023-05-18T11:52:56.41031+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:52:56.41038+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.859702ms 2023-05-18T11:52:56.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:01.40957+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.934895ms 2023-05-18T11:53:01.40965+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:01.40973+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.554098ms 2023-05-18T11:53:01.40977+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:06.41074+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.3333ms 2023-05-18T11:53:06.41081+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:06.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.167706ms 2023-05-18T11:53:06.41094+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:11.41055+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.034896ms 2023-05-18T11:53:11.41063+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:11.4107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.907903ms 2023-05-18T11:53:11.41074+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:16.4018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.665404ms 2023-05-18T11:53:16.40186+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:16.41008+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.182098ms 2023-05-18T11:53:16.41013+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:16.41084+08:00 ERROR [539043,23e49ee931c67717] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:53:21.41+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.182198ms 2023-05-18T11:53:21.41007+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:21.41012+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.142205ms 2023-05-18T11:53:21.41015+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:26.41153+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.830706ms 2023-05-18T11:53:26.41161+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:26.4117+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.869414ms 2023-05-18T11:53:26.41173+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:31.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.772093ms 2023-05-18T11:53:31.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:31.41061+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.634399ms 2023-05-18T11:53:31.41065+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:36.4121+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.048421ms 2023-05-18T11:53:36.41216+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:36.41224+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.042828ms 2023-05-18T11:53:36.41227+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:41.40926+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.054892ms 2023-05-18T11:53:41.40933+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:41.41026+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.194598ms 2023-05-18T11:53:41.41031+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:46.41669+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.932507ms 2023-05-18T11:53:46.41675+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:46.42461+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.798494ms 2023-05-18T11:53:46.42466+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:46.45666+08:00 ERROR [539043,8852fa529c5c955f] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:53:51.4107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.884595ms 2023-05-18T11:53:51.41076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:51.41083+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.926602ms 2023-05-18T11:53:51.41088+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:56.40973+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.720693ms 2023-05-18T11:53:56.4098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:53:56.40989+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.527298ms 2023-05-18T11:53:56.40993+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:01.40935+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.46629ms 2023-05-18T11:54:01.40943+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:01.40953+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.229594ms 2023-05-18T11:54:01.40956+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:06.41001+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.057796ms 2023-05-18T11:54:06.41008+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:06.41015+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.7289ms 2023-05-18T11:54:06.4102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:11.40298+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.106409ms 2023-05-18T11:54:11.40304+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:11.40874+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.264699ms 2023-05-18T11:54:11.40879+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:16.40234+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.088109ms 2023-05-18T11:54:16.40263+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:16.41374+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.83073ms 2023-05-18T11:54:16.4138+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:16.41429+08:00 ERROR [539043,48423030343c1888] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:54:21.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.230099ms 2023-05-18T11:54:21.4104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:21.41048+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.943803ms 2023-05-18T11:54:21.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:26.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.560591ms 2023-05-18T11:54:26.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:26.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.542598ms 2023-05-18T11:54:26.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:31.4091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.854789ms 2023-05-18T11:54:31.4092+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:31.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.159898ms 2023-05-18T11:54:31.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:36.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.648992ms 2023-05-18T11:54:36.41041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:36.41048+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.6516ms 2023-05-18T11:54:36.41052+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:41.40213+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.905206ms 2023-05-18T11:54:41.40219+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:41.40819+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.202798ms 2023-05-18T11:54:41.40824+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:46.42441+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.928514ms 2023-05-18T11:54:46.42447+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:46.42452+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.53871ms 2023-05-18T11:54:46.42455+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:46.44455+08:00 ERROR [539043,5613004366e597aa] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:54:51.41007+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.145997ms 2023-05-18T11:54:51.41013+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:51.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.909402ms 2023-05-18T11:54:51.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:56.40352+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.829818ms 2023-05-18T11:54:56.40361+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:54:56.41191+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.266599ms 2023-05-18T11:54:56.41199+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:01.4101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.715292ms 2023-05-18T11:55:01.41016+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:01.41023+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.461197ms 2023-05-18T11:55:01.41027+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:06.41005+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.034496ms 2023-05-18T11:55:06.41013+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:06.4102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.109005ms 2023-05-18T11:55:06.41023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:11.40871+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.440985ms 2023-05-18T11:55:11.40878+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:11.41003+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.825393ms 2023-05-18T11:55:11.41008+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:16.40157+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.596403ms 2023-05-18T11:55:16.40165+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:16.40171+08:00 ERROR [539043,288941d1f5996542] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:55:16.40791+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.141498ms 2023-05-18T11:55:16.40795+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:21.41071+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.906703ms 2023-05-18T11:55:21.41077+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:21.41081+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.158698ms 2023-05-18T11:55:21.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:26.41039+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.581802ms 2023-05-18T11:55:26.41045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:26.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.378308ms 2023-05-18T11:55:26.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:31.41141+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.511402ms 2023-05-18T11:55:31.41147+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:31.41154+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.632311ms 2023-05-18T11:55:31.41157+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:36.41018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.227106ms 2023-05-18T11:55:36.41025+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:36.41132+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.271099ms 2023-05-18T11:55:36.41137+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:41.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.213706ms 2023-05-18T11:55:41.41041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:41.41048+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.257724ms 2023-05-18T11:55:41.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:46.43199+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=26.899049ms 2023-05-18T11:55:46.43205+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:46.43211+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.582545ms 2023-05-18T11:55:46.43213+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:46.45332+08:00 ERROR [539043,ed0704a79cb0b249] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:55:51.41064+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.200907ms 2023-05-18T11:55:51.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:51.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.993321ms 2023-05-18T11:55:51.41082+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:56.40212+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.711513ms 2023-05-18T11:55:56.40219+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:55:56.40999+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.763401ms 2023-05-18T11:55:56.41004+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:01.41101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.403526ms 2023-05-18T11:56:01.41107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:01.41112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.47531ms 2023-05-18T11:56:01.41116+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:06.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.94122ms 2023-05-18T11:56:06.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:06.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.098806ms 2023-05-18T11:56:06.41052+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:11.41084+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.804501ms 2023-05-18T11:56:11.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:11.41098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.94102ms 2023-05-18T11:56:11.41101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:16.40243+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.785014ms 2023-05-18T11:56:16.40249+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:16.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.908302ms 2023-05-18T11:56:16.41048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:16.41116+08:00 ERROR [539043,c544dce18feaa74d] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:56:21.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.144505ms 2023-05-18T11:56:21.41046+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:21.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.005621ms 2023-05-18T11:56:21.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:26.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.034704ms 2023-05-18T11:56:26.41075+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:26.41082+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.192823ms 2023-05-18T11:56:26.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:31.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.253907ms 2023-05-18T11:56:31.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:31.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.298725ms 2023-05-18T11:56:31.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:36.41104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.158206ms 2023-05-18T11:56:36.41136+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:36.41184+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.849832ms 2023-05-18T11:56:36.41189+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:41.40988+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.231807ms 2023-05-18T11:56:41.40995+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:41.41002+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.845219ms 2023-05-18T11:56:41.41005+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:46.42157+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.016704ms 2023-05-18T11:56:46.42164+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:46.42169+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.438126ms 2023-05-18T11:56:46.42172+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:46.46915+08:00 ERROR [539043,d97f5196b8f10abd] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:56:51.40751+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=14.140884ms 2023-05-18T11:56:51.40759+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:51.41015+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.172206ms 2023-05-18T11:56:51.4102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:56.41374+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=20.334664ms 2023-05-18T11:56:56.41381+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:56:56.4139+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.481649ms 2023-05-18T11:56:56.41394+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:01.41066+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.129606ms 2023-05-18T11:57:01.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:01.41081+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.280425ms 2023-05-18T11:57:01.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:06.41011+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.151405ms 2023-05-18T11:57:06.41018+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:06.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.182623ms 2023-05-18T11:57:06.41031+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:11.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.851402ms 2023-05-18T11:57:11.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:11.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.89322ms 2023-05-18T11:57:11.41068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:16.40219+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.766914ms 2023-05-18T11:57:16.40225+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:16.4102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.909503ms 2023-05-18T11:57:16.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:16.41094+08:00 ERROR [539043,da04b75b9ddbefb0] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:57:21.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.024404ms 2023-05-18T11:57:21.41082+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:21.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.192724ms 2023-05-18T11:57:21.41094+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:26.40308+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.083631ms 2023-05-18T11:57:26.40314+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:26.4101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.103006ms 2023-05-18T11:57:26.41015+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:31.41123+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.329508ms 2023-05-18T11:57:31.4113+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:31.41139+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.619129ms 2023-05-18T11:57:31.41142+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:36.41276+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.704725ms 2023-05-18T11:57:36.41283+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:36.41291+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.872944ms 2023-05-18T11:57:36.41294+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:41.41078+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.034004ms 2023-05-18T11:57:41.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:41.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.571028ms 2023-05-18T11:57:41.41094+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:46.41523+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.782414ms 2023-05-18T11:57:46.4153+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:46.42331+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.942003ms 2023-05-18T11:57:46.42336+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:46.45865+08:00 ERROR [539043,3f9e1e7c7b6c4662] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:57:51.41211+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.651325ms 2023-05-18T11:57:51.41219+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:51.41227+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.567141ms 2023-05-18T11:57:51.4123+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:56.40994+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.993203ms 2023-05-18T11:57:56.41001+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:57:56.41008+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.890919ms 2023-05-18T11:57:56.41011+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:01.41088+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.089705ms 2023-05-18T11:58:01.41094+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:01.41104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.131922ms 2023-05-18T11:58:01.41107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:06.4068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.413874ms 2023-05-18T11:58:06.40689+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:06.41019+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.079805ms 2023-05-18T11:58:06.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:11.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.54541ms 2023-05-18T11:58:11.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:11.41088+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.679029ms 2023-05-18T11:58:11.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:16.40174+08:00 ERROR [539043,94df9fe42f7adc9c] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:58:16.40269+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.968317ms 2023-05-18T11:58:16.40275+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:16.40897+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.51431ms 2023-05-18T11:58:16.40902+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:21.40611+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.784766ms 2023-05-18T11:58:21.40617+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:21.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.623412ms 2023-05-18T11:58:21.41083+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:26.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.375508ms 2023-05-18T11:58:26.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:26.41094+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.539227ms 2023-05-18T11:58:26.41097+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:31.41001+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.356013ms 2023-05-18T11:58:31.41007+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:31.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.976604ms 2023-05-18T11:58:31.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:36.41089+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.340308ms 2023-05-18T11:58:36.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:36.41106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.790631ms 2023-05-18T11:58:36.41109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:41.41014+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.014904ms 2023-05-18T11:58:41.41021+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:41.41028+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.94232ms 2023-05-18T11:58:41.41031+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:46.42922+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=21.621881ms 2023-05-18T11:58:46.42929+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:46.42937+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=21.264276ms 2023-05-18T11:58:46.4294+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:46.44203+08:00 ERROR [539043,8caaef4f53d3259c] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:58:51.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.136106ms 2023-05-18T11:58:51.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:51.4107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.179023ms 2023-05-18T11:58:51.41073+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:56.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.063904ms 2023-05-18T11:58:56.41027+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:58:56.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.177923ms 2023-05-18T11:58:56.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:01.40192+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.961917ms 2023-05-18T11:59:01.40201+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:01.40956+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.936516ms 2023-05-18T11:59:01.40962+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:06.4016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.637712ms 2023-05-18T11:59:06.40166+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:06.4085+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.885703ms 2023-05-18T11:59:06.40855+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:11.41322+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.278151ms 2023-05-18T11:59:11.41329+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:11.41424+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.815015ms 2023-05-18T11:59:11.4143+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:16.40212+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.966216ms 2023-05-18T11:59:16.40218+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:16.41029+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.075005ms 2023-05-18T11:59:16.41034+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:16.41156+08:00 ERROR [539043,71ce340c34e42d9a] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:59:21.40204+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.937216ms 2023-05-18T11:59:21.40211+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:21.40833+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.264307ms 2023-05-18T11:59:21.40839+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:26.41075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.058105ms 2023-05-18T11:59:26.41083+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:26.41094+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.022321ms 2023-05-18T11:59:26.41097+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:31.40233+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.939216ms 2023-05-18T11:59:31.40242+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:31.4081+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.041905ms 2023-05-18T11:59:31.40815+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:36.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.951903ms 2023-05-18T11:59:36.4104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:36.41048+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.057821ms 2023-05-18T11:59:36.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:41.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.025805ms 2023-05-18T11:59:41.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:41.41092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.231023ms 2023-05-18T11:59:41.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:46.4139+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.889829ms 2023-05-18T11:59:46.41396+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:46.43043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=25.856635ms 2023-05-18T11:59:46.43048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:46.46053+08:00 ERROR [539043,302e18b223d740f0] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T11:59:51.40749+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.706978ms 2023-05-18T11:59:51.40756+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:51.41261+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.905229ms 2023-05-18T11:59:51.41267+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:56.41048+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.48781ms 2023-05-18T11:59:56.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T11:59:56.41065+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.226224ms 2023-05-18T11:59:56.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:01.4091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.548401ms 2023-05-18T12:00:01.40917+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:01.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.069305ms 2023-05-18T12:00:01.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:06.40313+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.130231ms 2023-05-18T12:00:06.40321+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:06.40955+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.985704ms 2023-05-18T12:00:06.40961+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:11.40296+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.988717ms 2023-05-18T12:00:11.40304+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:11.40873+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.177406ms 2023-05-18T12:00:11.40878+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:16.40239+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.079518ms 2023-05-18T12:00:16.40245+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:16.411+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.506311ms 2023-05-18T12:00:16.41105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:16.41178+08:00 ERROR [539043,ce1ff48626a9c48b] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:00:16.4282+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields:, module=monitor.ob, duration="21.4µs" 2023-05-18T12:00:16.42829+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields:, module=monitor.ob, eventType=add, duration="6.9µs" 2023-05-18T12:00:16.42832+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields:, module=monitor.ob, duration="5µs" 2023-05-18T12:00:16.42836+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields: module=monitor.ob, eventType=add, duration="6.2µs" 2023-05-18T12:00:16.4284+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T12:00:16.43214+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc0009f6640 0xc0009f66e0 0xc0009f6780 0xc0009f6820 0xc0009f68c0 0xc0009f6960 0xc0009f6a00 0xc0009f6aa0 0xc0009f6b40 0xc0009f6be0 0xc0009f6c80 0xc0009f6d20 0xc0009f6dc0 0xc0009f6e60 0xc0009f6f00 0xc0009f6fa0 0xc0009f7040 0xc0009f70e0 0xc0009f7180 0xc0009f7220 0xc0009f72c0 0xc0009f7360 0xc0009f7400 0xc0009f74a0 0xc0009f7540 0xc0009f75e0 0xc0009f7680 0xc0009f7720 0xc0009f77c0 0xc0009f7860 0xc0009f7900] CollectInterval:1s TimeAlign:false} 2023-05-18T12:00:16.43293+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T12:00:16.43296+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields: input=mysqlTableInput, duration="4.7µs" 2023-05-18T12:00:16.43298+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields:, input=mysqlTableInput, duration="25.8µs" 2023-05-18T12:00:16.43302+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields: eventType=add, error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)", duration=4.664861ms, module=monitor.ob 2023-05-18T12:00:16.43306+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields:, module=monitor.ob, eventType=add, duration=4.696561ms 2023-05-18T12:00:16.43308+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields:, module=monitor.ob, duration=4.767261ms 2023-05-18T12:00:16.4331+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields:, module=monitor.ob, eventType=add, duration=4.816963ms 2023-05-18T12:00:16.43311+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields:, module=monitor.ob, duration=4.930964ms 2023-05-18T12:00:16.43313+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 9 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T12:00:21.40187+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.674213ms 2023-05-18T12:00:21.40193+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:21.41003+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.071805ms 2023-05-18T12:00:21.41008+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:26.40905+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.079896ms 2023-05-18T12:00:26.40913+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:26.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.867202ms 2023-05-18T12:00:26.4104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:31.41165+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.722213ms 2023-05-18T12:00:31.41172+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:31.41182+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.117035ms 2023-05-18T12:00:31.41185+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:36.40993+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.956004ms 2023-05-18T12:00:36.40999+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:36.41006+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.881419ms 2023-05-18T12:00:36.41009+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:41.40572+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.170758ms 2023-05-18T12:00:41.40579+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:41.41222+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.214607ms 2023-05-18T12:00:41.41227+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:46.4157+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.21442ms 2023-05-18T12:00:46.41578+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:46.42477+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.876615ms 2023-05-18T12:00:46.42484+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:46.45179+08:00 ERROR [539043,6806fea0b6279a6a] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:00:51.41+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.957803ms 2023-05-18T12:00:51.41009+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:51.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.706117ms 2023-05-18T12:00:51.4102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:56.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.168206ms 2023-05-18T12:00:56.41076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:00:56.41084+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.96542ms 2023-05-18T12:00:56.41087+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:01.4115+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.571111ms 2023-05-18T12:01:01.41158+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:01.41167+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.691029ms 2023-05-18T12:01:01.4117+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:06.41041+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.072105ms 2023-05-18T12:01:06.41048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:06.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.183023ms 2023-05-18T12:01:06.41066+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:11.40945+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.821106ms 2023-05-18T12:01:11.40951+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:11.41113+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.533411ms 2023-05-18T12:01:11.41118+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:16.40288+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.920416ms 2023-05-18T12:01:16.40295+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:16.41115+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.158005ms 2023-05-18T12:01:16.4112+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:16.41183+08:00 ERROR [539043,05cec422da8cef22] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:01:21.41005+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.839219ms 2023-05-18T12:01:21.41011+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:21.41018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.141405ms 2023-05-18T12:01:21.41021+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:26.40981+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.068504ms 2023-05-18T12:01:26.40987+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:26.40995+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.798218ms 2023-05-18T12:01:26.40998+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:31.41074+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.915503ms 2023-05-18T12:01:31.41082+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:31.411+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.198023ms 2023-05-18T12:01:31.41104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:36.41018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.013704ms 2023-05-18T12:01:36.41025+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:36.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.98392ms 2023-05-18T12:01:36.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:41.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.504911ms 2023-05-18T12:01:41.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:41.41074+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.376725ms 2023-05-18T12:01:41.41077+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:46.40647+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.944016ms 2023-05-18T12:01:46.40653+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:46.4147+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.140805ms 2023-05-18T12:01:46.41475+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:46.45371+08:00 ERROR [539043,f5f46e3562727b71] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:01:51.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.176523ms 2023-05-18T12:01:51.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:51.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.352708ms 2023-05-18T12:01:51.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:56.41108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.279808ms 2023-05-18T12:01:56.41114+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:01:56.41127+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.339025ms 2023-05-18T12:01:56.41133+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:01.40475+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.504749ms 2023-05-18T12:02:01.40484+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:01.41071+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.639912ms 2023-05-18T12:02:01.41076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:06.41092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.43101ms 2023-05-18T12:02:06.411+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:06.41108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.454327ms 2023-05-18T12:02:06.41111+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:11.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.279108ms 2023-05-18T12:02:11.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:11.41085+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.427627ms 2023-05-18T12:02:11.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:16.40285+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.025017ms 2023-05-18T12:02:16.40293+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:16.41108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.109005ms 2023-05-18T12:02:16.41114+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:16.41178+08:00 ERROR [539043,e0efe81f9c2c3ded] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:02:21.41082+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.368108ms 2023-05-18T12:02:21.41088+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:21.41097+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.469926ms 2023-05-18T12:02:21.41101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:26.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.136705ms 2023-05-18T12:02:26.41098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:26.41105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.268724ms 2023-05-18T12:02:26.41108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:31.41012+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.203707ms 2023-05-18T12:02:31.41017+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:31.41024+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.101522ms 2023-05-18T12:02:31.41027+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:36.40196+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.985716ms 2023-05-18T12:02:36.40203+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:36.40873+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.109005ms 2023-05-18T12:02:36.40878+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:41.4117+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.791614ms 2023-05-18T12:02:41.41177+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:41.41184+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.839831ms 2023-05-18T12:02:41.41187+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:46.4316+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.285241ms 2023-05-18T12:02:46.43166+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:46.43176+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=25.933236ms 2023-05-18T12:02:46.43179+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:46.45317+08:00 ERROR [539043,f525fa609eca1b8a] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:02:51.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.015704ms 2023-05-18T12:02:51.41041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:51.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.079622ms 2023-05-18T12:02:51.41053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:56.40861+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.887893ms 2023-05-18T12:02:56.40869+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:02:56.41177+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.203519ms 2023-05-18T12:02:56.41184+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:01.41015+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.154606ms 2023-05-18T12:03:01.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:01.41029+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.834919ms 2023-05-18T12:03:01.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:06.41061+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.298207ms 2023-05-18T12:03:06.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:06.41075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.087222ms 2023-05-18T12:03:06.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:11.4119+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.354822ms 2023-05-18T12:03:11.41198+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:11.41209+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.307037ms 2023-05-18T12:03:11.41212+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:16.40276+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.515724ms 2023-05-18T12:03:16.40283+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:16.41084+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.968704ms 2023-05-18T12:03:16.41088+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:16.41149+08:00 ERROR [539043,71364f3065d00217] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:03:21.41172+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.708913ms 2023-05-18T12:03:21.41179+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:21.41189+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.030534ms 2023-05-18T12:03:21.41193+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:26.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.132805ms 2023-05-18T12:03:26.41041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:26.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.175623ms 2023-05-18T12:03:26.41052+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:31.40222+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.496811ms 2023-05-18T12:03:31.40229+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:31.40828+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.973303ms 2023-05-18T12:03:31.40834+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:36.41019+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.049405ms 2023-05-18T12:03:36.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:36.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.126322ms 2023-05-18T12:03:36.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:41.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.845402ms 2023-05-18T12:03:41.4106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:41.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.628216ms 2023-05-18T12:03:41.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:46.41923+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.334208ms 2023-05-18T12:03:46.4193+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:46.4194+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.547654ms 2023-05-18T12:03:46.41943+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:46.4601+08:00 ERROR [539043,f8ac4e0b00d8b545] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:03:51.40291+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.927216ms 2023-05-18T12:03:51.40298+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:51.40768+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.068105ms 2023-05-18T12:03:51.40773+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:56.4107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.216107ms 2023-05-18T12:03:56.41077+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:03:56.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.855919ms 2023-05-18T12:03:56.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:01.41047+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.909403ms 2023-05-18T12:04:01.41055+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:01.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.087822ms 2023-05-18T12:04:01.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:06.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.190906ms 2023-05-18T12:04:06.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:06.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.253324ms 2023-05-18T12:04:06.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:11.40973+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.993604ms 2023-05-18T12:04:11.40985+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:11.40994+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.804318ms 2023-05-18T12:04:11.40997+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:16.40232+08:00 ERROR [539043,b69bc89918ee0282] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:04:16.40246+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.788218ms 2023-05-18T12:04:16.4025+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:16.40855+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.321912ms 2023-05-18T12:04:16.40861+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:21.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.045508ms 2023-05-18T12:04:21.41054+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:21.41064+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.326433ms 2023-05-18T12:04:21.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:26.40782+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.17859ms 2023-05-18T12:04:26.40788+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:26.41102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.280711ms 2023-05-18T12:04:26.41107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:31.41028+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.18801ms 2023-05-18T12:04:31.41059+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:31.41108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.712538ms 2023-05-18T12:04:31.41112+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:36.41061+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.282112ms 2023-05-18T12:04:36.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:36.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.337133ms 2023-05-18T12:04:36.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:41.40318+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.322926ms 2023-05-18T12:04:41.40326+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:41.40845+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.973408ms 2023-05-18T12:04:41.4085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:46.41599+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.809519ms 2023-05-18T12:04:46.41605+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:46.425+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.869019ms 2023-05-18T12:04:46.42506+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:46.45669+08:00 ERROR [539043,a3fb3c61c267f485] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:04:51.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.19051ms 2023-05-18T12:04:51.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:51.41048+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.387634ms 2023-05-18T12:04:51.41052+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:56.41041+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.983308ms 2023-05-18T12:04:56.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:04:56.41054+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.787426ms 2023-05-18T12:04:56.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:01.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.19091ms 2023-05-18T12:05:01.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:01.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.982328ms 2023-05-18T12:05:01.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:06.40719+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.468681ms 2023-05-18T12:05:06.40726+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:06.41104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.105509ms 2023-05-18T12:05:06.4111+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:11.40267+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.817618ms 2023-05-18T12:05:11.40275+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:11.4087+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.158209ms 2023-05-18T12:05:11.40875+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:16.40206+08:00 ERROR [539043,40396a301048c505] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:05:16.40217+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.94592ms 2023-05-18T12:05:16.40223+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:16.40794+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.067009ms 2023-05-18T12:05:16.40801+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:21.40602+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.521568ms 2023-05-18T12:05:21.40608+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:21.4112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.223411ms 2023-05-18T12:05:21.41125+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:26.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.102209ms 2023-05-18T12:05:26.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:26.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.847827ms 2023-05-18T12:05:26.41033+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:31.40187+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.494214ms 2023-05-18T12:05:31.40193+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:31.40953+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.564002ms 2023-05-18T12:05:31.40959+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:36.40639+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.275179ms 2023-05-18T12:05:36.40646+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:36.40998+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.132809ms 2023-05-18T12:05:36.41003+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:41.40187+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.87672ms 2023-05-18T12:05:41.40194+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:41.40802+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.262012ms 2023-05-18T12:05:41.40807+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:46.41853+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.890547ms 2023-05-18T12:05:46.41861+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:46.43464+08:00 ERROR [539043,b0e153eef9b52567] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:05:46.43475+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=26.503957ms 2023-05-18T12:05:46.43479+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:51.40253+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.898219ms 2023-05-18T12:05:51.40261+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:51.40829+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.055308ms 2023-05-18T12:05:51.40835+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:56.41006+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.992208ms 2023-05-18T12:05:56.41012+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:05:56.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.10133ms 2023-05-18T12:05:56.41025+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:01.41001+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.700804ms 2023-05-18T12:06:01.41009+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:01.41016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.629424ms 2023-05-18T12:06:01.4102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:06.40861+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.448708ms 2023-05-18T12:06:06.4087+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:06.41055+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.431813ms 2023-05-18T12:06:06.41063+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:11.41051+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.068308ms 2023-05-18T12:06:11.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:11.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.02563ms 2023-05-18T12:06:11.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:16.40274+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.90842ms 2023-05-18T12:06:16.4028+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:16.41065+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.814305ms 2023-05-18T12:06:16.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:16.41135+08:00 ERROR [539043,73c9e9eca21dbe83] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:06:21.41023+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.869805ms 2023-05-18T12:06:21.41031+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:21.41039+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.610724ms 2023-05-18T12:06:21.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:26.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.762105ms 2023-05-18T12:06:26.4106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:26.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.666024ms 2023-05-18T12:06:26.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:31.40986+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.547001ms 2023-05-18T12:06:31.40992+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:31.41002+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.40232ms 2023-05-18T12:06:31.41005+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:36.41026+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.677104ms 2023-05-18T12:06:36.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:36.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.015329ms 2023-05-18T12:06:36.41046+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:41.41085+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.383612ms 2023-05-18T12:06:41.41092+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:41.41098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.176131ms 2023-05-18T12:06:41.41101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:46.41631+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.856519ms 2023-05-18T12:06:46.41638+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:46.45429+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.010316ms 2023-05-18T12:06:46.45435+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:46.4739+08:00 ERROR [539043,0293b56ab0b0c04d] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:06:51.41009+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.741404ms 2023-05-18T12:06:51.41016+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:51.41023+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.577523ms 2023-05-18T12:06:51.41025+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:56.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.097809ms 2023-05-18T12:06:56.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:06:56.41048+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.046329ms 2023-05-18T12:06:56.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:01.40574+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.439754ms 2023-05-18T12:07:01.40581+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:01.41339+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.538701ms 2023-05-18T12:07:01.41343+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:06.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.723204ms 2023-05-18T12:07:06.41065+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:06.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.911027ms 2023-05-18T12:07:06.41076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:11.40442+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.369739ms 2023-05-18T12:07:11.40448+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:11.41282+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.905033ms 2023-05-18T12:07:11.41289+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:16.40248+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.163023ms 2023-05-18T12:07:16.40254+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:16.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.967207ms 2023-05-18T12:07:16.41065+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:16.41134+08:00 ERROR [539043,39335cd5cbdfeb1b] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:07:21.40239+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.860619ms 2023-05-18T12:07:21.40245+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:21.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.002108ms 2023-05-18T12:07:21.41054+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:26.40313+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.140937ms 2023-05-18T12:07:26.4032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:26.40953+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.870506ms 2023-05-18T12:07:26.40959+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:31.4108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.041508ms 2023-05-18T12:07:31.41088+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:31.41095+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.281433ms 2023-05-18T12:07:31.41099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:36.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.033509ms 2023-05-18T12:07:36.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:36.41065+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.013928ms 2023-05-18T12:07:36.41068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:41.40796+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=14.965901ms 2023-05-18T12:07:41.40804+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:41.40992+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.17061ms 2023-05-18T12:07:41.40997+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:46.41707+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.149823ms 2023-05-18T12:07:46.41716+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:46.44796+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.330825ms 2023-05-18T12:07:46.44802+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:46.48329+08:00 ERROR [539043,d23dc5ff864e0570] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:07:51.40313+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.142336ms 2023-05-18T12:07:51.4032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:51.40939+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.686403ms 2023-05-18T12:07:51.40944+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:56.40994+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.038009ms 2023-05-18T12:07:56.41+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:07:56.41009+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.990829ms 2023-05-18T12:07:56.41012+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:01.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.114609ms 2023-05-18T12:08:01.41074+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:01.41082+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.017429ms 2023-05-18T12:08:01.41086+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:06.41347+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.939168ms 2023-05-18T12:08:06.41353+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:06.41361+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.393454ms 2023-05-18T12:08:06.41364+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:11.40989+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.993308ms 2023-05-18T12:08:11.40996+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:11.41006+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.744125ms 2023-05-18T12:08:11.41009+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:16.40243+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.254624ms 2023-05-18T12:08:16.40251+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:16.41064+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.093009ms 2023-05-18T12:08:16.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:16.41139+08:00 ERROR [539043,1318cdefc73dc0af] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:08:21.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.779204ms 2023-05-18T12:08:21.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:21.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.03163ms 2023-05-18T12:08:21.41076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:26.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.706704ms 2023-05-18T12:08:26.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:26.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.719625ms 2023-05-18T12:08:26.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:31.40606+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.073976ms 2023-05-18T12:08:31.40613+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:31.40998+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.893006ms 2023-05-18T12:08:31.41003+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:36.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.004308ms 2023-05-18T12:08:36.4104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:36.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.751625ms 2023-05-18T12:08:36.41053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:41.41095+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.401813ms 2023-05-18T12:08:41.41104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:41.41112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.458435ms 2023-05-18T12:08:41.41115+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:46.4507+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.578758ms 2023-05-18T12:08:46.45077+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:46.45084+08:00 ERROR [539043,3f98a8eb49b8b20b] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:08:46.45092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=27.281867ms 2023-05-18T12:08:46.45095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:51.41085+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.341913ms 2023-05-18T12:08:51.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:51.411+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.408235ms 2023-05-18T12:08:51.41103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:56.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.20331ms 2023-05-18T12:08:56.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:08:56.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.139831ms 2023-05-18T12:08:56.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:01.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.18051ms 2023-05-18T12:09:01.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:01.41075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.964028ms 2023-05-18T12:09:01.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:06.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.033608ms 2023-05-18T12:09:06.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:06.41061+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.08693ms 2023-05-18T12:09:06.41065+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:11.41085+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.461913ms 2023-05-18T12:09:11.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:11.41098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.989828ms 2023-05-18T12:09:11.41101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:16.40269+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.209923ms 2023-05-18T12:09:16.40276+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:16.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.111109ms 2023-05-18T12:09:16.41095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:16.41166+08:00 ERROR [539043,06c2434a3c02ac3d] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:09:21.41129+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.099209ms 2023-05-18T12:09:21.41136+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:21.41143+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.423234ms 2023-05-18T12:09:21.41146+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:26.4102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.139209ms 2023-05-18T12:09:26.41027+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:26.41037+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.142731ms 2023-05-18T12:09:26.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:31.40809+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=14.441894ms 2023-05-18T12:09:31.40817+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:31.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.902206ms 2023-05-18T12:09:31.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:36.41087+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.235311ms 2023-05-18T12:09:36.41095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:36.41104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.190631ms 2023-05-18T12:09:36.41109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:41.40965+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.689804ms 2023-05-18T12:09:41.40972+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:41.40998+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.895927ms 2023-05-18T12:09:41.41002+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:46.41359+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.122104ms 2023-05-18T12:09:46.41366+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:46.43066+08:00 ERROR [539043,5726229f356e14f3] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:09:46.43075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=25.431842ms 2023-05-18T12:09:46.4308+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:51.40769+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=14.689698ms 2023-05-18T12:09:51.40776+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:51.40989+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.892607ms 2023-05-18T12:09:51.40994+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:56.41029+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.743104ms 2023-05-18T12:09:56.41036+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:09:56.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.481822ms 2023-05-18T12:09:56.41046+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:01.40181+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.597416ms 2023-05-18T12:10:01.40187+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:01.40788+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.046008ms 2023-05-18T12:10:01.40793+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:06.40256+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.91322ms 2023-05-18T12:10:06.40263+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:06.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.760605ms 2023-05-18T12:10:06.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:11.40236+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.719917ms 2023-05-18T12:10:11.40244+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:11.40821+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.939907ms 2023-05-18T12:10:11.40827+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:16.40214+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.970121ms 2023-05-18T12:10:16.4022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:16.41036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.108909ms 2023-05-18T12:10:16.4104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:16.41108+08:00 ERROR [539043,e3dd5b4e0722e0a9] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:10:16.43342+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields:, module=monitor.ob, duration="18.901µs" 2023-05-18T12:10:16.43348+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields:, eventType=add, module=monitor.ob, duration="5.6µs" 2023-05-18T12:10:16.43351+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields: module=monitor.ob, duration="4.9µs" 2023-05-18T12:10:16.43356+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields:, module=monitor.ob, eventType=add, duration="6.001µs" 2023-05-18T12:10:16.43361+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T12:10:16.43739+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc000278640 0xc0002786e0 0xc000278780 0xc000278820 0xc0002788c0 0xc000278960 0xc000278a00 0xc000278aa0 0xc000278b40 0xc000278be0 0xc000278c80 0xc000278d20 0xc000278dc0 0xc000278e60 0xc000278f00 0xc000278fa0 0xc000279040 0xc0002790e0 0xc000279180 0xc000279220 0xc0002792c0 0xc000279360 0xc000279400 0xc0002794a0 0xc000279540 0xc0002795e0 0xc000279680 0xc000279720 0xc0002797c0 0xc000279860 0xc000279900] CollectInterval:1s TimeAlign:false} 2023-05-18T12:10:16.43817+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T12:10:16.4382+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields:, input=mysqlTableInput, duration="4µs" 2023-05-18T12:10:16.43822+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields: input=mysqlTableInput, duration="22.2µs" 2023-05-18T12:10:16.43824+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields: duration=4.681963ms, module=monitor.ob, eventType=add, error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:10:16.43826+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields:, module=monitor.ob, eventType=add, duration=4.700264ms 2023-05-18T12:10:16.43827+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields: module=monitor.ob, duration=4.770964ms 2023-05-18T12:10:16.43829+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields: module=monitor.ob, eventType=add, duration=4.813665ms 2023-05-18T12:10:16.4383+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields: duration=4.899566ms, module=monitor.ob 2023-05-18T12:10:16.43832+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 10 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T12:10:21.40219+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.022321ms 2023-05-18T12:10:21.40226+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:21.4089+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.745218ms 2023-05-18T12:10:21.40895+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:26.40986+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.603703ms 2023-05-18T12:10:26.40993+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:26.41+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.40662ms 2023-05-18T12:10:26.41003+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:31.40987+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.756005ms 2023-05-18T12:10:31.40994+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:31.41001+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.743325ms 2023-05-18T12:10:31.41004+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:36.41148+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.377313ms 2023-05-18T12:10:36.41154+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:36.41163+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.697538ms 2023-05-18T12:10:36.41166+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:41.40935+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.61721ms 2023-05-18T12:10:41.40942+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:41.41016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.853805ms 2023-05-18T12:10:41.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:46.42509+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.493428ms 2023-05-18T12:10:46.42517+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:46.42532+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.78326ms 2023-05-18T12:10:46.42539+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:46.47538+08:00 ERROR [539043,6c1b2a20d1c7c8df] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:10:51.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.592323ms 2023-05-18T12:10:51.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:51.41184+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.838806ms 2023-05-18T12:10:51.41189+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:56.4102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.127909ms 2023-05-18T12:10:56.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:10:56.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.828526ms 2023-05-18T12:10:56.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:01.40728+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.338779ms 2023-05-18T12:11:01.40734+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:01.4109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.066009ms 2023-05-18T12:11:01.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:06.40975+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.687603ms 2023-05-18T12:11:06.40982+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:06.4101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.961328ms 2023-05-18T12:11:06.41014+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:11.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.957107ms 2023-05-18T12:11:11.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:11.41087+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.900427ms 2023-05-18T12:11:11.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:16.40233+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.91272ms 2023-05-18T12:11:16.40245+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:16.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.798605ms 2023-05-18T12:11:16.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:16.41108+08:00 ERROR [539043,eaab5f9058bc65f4] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:11:21.40438+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.41294ms 2023-05-18T12:11:21.40444+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:21.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.674503ms 2023-05-18T12:11:21.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:26.40998+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.114717ms 2023-05-18T12:11:26.41004+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:26.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.17401ms 2023-05-18T12:11:26.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:31.40966+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.674003ms 2023-05-18T12:11:31.40973+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:31.40982+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.407221ms 2023-05-18T12:11:31.40986+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:36.40186+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.627916ms 2023-05-18T12:11:36.40194+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:36.40775+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.914007ms 2023-05-18T12:11:36.4078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:41.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.17261ms 2023-05-18T12:11:41.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:41.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.222931ms 2023-05-18T12:11:41.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:46.44388+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=35.66828ms 2023-05-18T12:11:46.44394+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:46.44399+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=36.314789ms 2023-05-18T12:11:46.44402+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:46.46402+08:00 ERROR [539043,bf45b0a9301537fb] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:11:51.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.840019ms 2023-05-18T12:11:51.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:51.41076+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.598437ms 2023-05-18T12:11:51.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:56.40322+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.162823ms 2023-05-18T12:11:56.4033+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:11:56.40863+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.866319ms 2023-05-18T12:11:56.40869+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:01.41026+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.974707ms 2023-05-18T12:12:01.41033+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:01.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.732225ms 2023-05-18T12:12:01.41046+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:06.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.045108ms 2023-05-18T12:12:06.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:06.41075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.229231ms 2023-05-18T12:12:06.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:11.41015+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.757304ms 2023-05-18T12:12:11.41021+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:11.41029+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.002129ms 2023-05-18T12:12:11.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:16.40212+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.90492ms 2023-05-18T12:12:16.40218+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:16.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.046309ms 2023-05-18T12:12:16.41031+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:16.411+08:00 ERROR [539043,3c0c8d9854ffee13] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:12:21.4101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.135509ms 2023-05-18T12:12:21.41017+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:21.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.106231ms 2023-05-18T12:12:21.4103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:26.41322+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.185958ms 2023-05-18T12:12:26.41329+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:26.41396+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.222824ms 2023-05-18T12:12:26.41404+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:31.41099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.060908ms 2023-05-18T12:12:31.41106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:31.41116+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.167531ms 2023-05-18T12:12:31.41119+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:36.4112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.573415ms 2023-05-18T12:12:36.41128+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:36.41135+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.551236ms 2023-05-18T12:12:36.41138+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:41.40424+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.527941ms 2023-05-18T12:12:41.40432+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:41.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.806405ms 2023-05-18T12:12:41.41045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:46.41744+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.678144ms 2023-05-18T12:12:46.4175+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:46.42564+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.029608ms 2023-05-18T12:12:46.4257+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:46.45166+08:00 ERROR [539043,03c1138834c4aaa5] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:12:51.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.912704ms 2023-05-18T12:12:51.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:51.41054+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.063225ms 2023-05-18T12:12:51.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:56.41322+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.844162ms 2023-05-18T12:12:56.41354+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:12:56.41486+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.883317ms 2023-05-18T12:12:56.41491+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:01.406+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.836569ms 2023-05-18T12:13:01.40607+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:01.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.241308ms 2023-05-18T12:13:01.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:06.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.591801ms 2023-05-18T12:13:06.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:06.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.551018ms 2023-05-18T12:13:06.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:11.4122+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.817129ms 2023-05-18T12:13:11.41226+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:11.41235+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.739747ms 2023-05-18T12:13:11.41238+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:16.40207+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.006219ms 2023-05-18T12:13:16.40213+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:16.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.993205ms 2023-05-18T12:13:16.41023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:16.41092+08:00 ERROR [539043,d96c239bd3eaff54] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:13:21.41018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.667901ms 2023-05-18T12:13:21.41025+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:21.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.64942ms 2023-05-18T12:13:21.41036+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:26.4102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.900704ms 2023-05-18T12:13:26.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:26.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.933224ms 2023-05-18T12:13:26.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:31.41037+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.021106ms 2023-05-18T12:13:31.41044+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:31.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.961124ms 2023-05-18T12:13:31.41055+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:36.41071+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.31471ms 2023-05-18T12:13:36.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:36.41089+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.589932ms 2023-05-18T12:13:36.41092+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:41.40964+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.827003ms 2023-05-18T12:13:41.40971+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:41.4098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.579718ms 2023-05-18T12:13:41.40983+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:46.41649+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.860817ms 2023-05-18T12:13:46.41656+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:46.42468+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.029606ms 2023-05-18T12:13:46.42473+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:46.45237+08:00 ERROR [539043,4065c5e548da439f] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:13:51.41074+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.018306ms 2023-05-18T12:13:51.41082+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:51.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.964024ms 2023-05-18T12:13:51.41094+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:56.41076+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.979105ms 2023-05-18T12:13:56.41082+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:13:56.41092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.952524ms 2023-05-18T12:13:56.41095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:01.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.31281ms 2023-05-18T12:14:01.41048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:01.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.916124ms 2023-05-18T12:14:01.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:06.40305+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.09092ms 2023-05-18T12:14:06.40312+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:06.40854+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.945905ms 2023-05-18T12:14:06.4086+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:11.41059+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.499412ms 2023-05-18T12:14:11.41066+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:11.41074+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.241828ms 2023-05-18T12:14:11.41077+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:16.40195+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.708915ms 2023-05-18T12:14:16.40201+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:16.40989+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.842603ms 2023-05-18T12:14:16.40994+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:16.41068+08:00 ERROR [539043,f68607840d3e00fc] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:14:21.41132+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.154208ms 2023-05-18T12:14:21.41139+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:21.41148+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.830836ms 2023-05-18T12:14:21.41151+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:26.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.28561ms 2023-05-18T12:14:26.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:26.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.253628ms 2023-05-18T12:14:26.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:31.40535+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.447251ms 2023-05-18T12:14:31.40541+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:31.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.138308ms 2023-05-18T12:14:31.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:36.40146+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.504212ms 2023-05-18T12:14:36.40152+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:36.40878+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.154408ms 2023-05-18T12:14:36.40883+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:41.41088+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.966805ms 2023-05-18T12:14:41.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:41.41103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.131826ms 2023-05-18T12:14:41.41106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:46.4357+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=27.495163ms 2023-05-18T12:14:46.43577+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:46.43582+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=28.116671ms 2023-05-18T12:14:46.43585+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:46.45569+08:00 ERROR [539043,cd8bd837b2c48efd] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:14:51.40269+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.986119ms 2023-05-18T12:14:51.40279+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:51.40827+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.957305ms 2023-05-18T12:14:51.40832+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:56.40303+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.032619ms 2023-05-18T12:14:56.4031+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:14:56.40984+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.233435ms 2023-05-18T12:14:56.40989+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:01.40765+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.681694ms 2023-05-18T12:15:01.40772+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:01.40937+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.896804ms 2023-05-18T12:15:01.40941+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:06.40564+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.405351ms 2023-05-18T12:15:06.40571+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:06.41343+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.679501ms 2023-05-18T12:15:06.41348+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:11.41078+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.141307ms 2023-05-18T12:15:11.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:11.41093+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.158426ms 2023-05-18T12:15:11.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:16.40226+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.268322ms 2023-05-18T12:15:16.40232+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:16.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.999006ms 2023-05-18T12:15:16.41045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:16.41117+08:00 ERROR [539043,e52f80e0a53fe6b0] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:15:21.41015+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.412517ms 2023-05-18T12:15:21.41021+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:21.41199+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.426811ms 2023-05-18T12:15:21.41204+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:26.40992+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.215214ms 2023-05-18T12:15:26.40999+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:26.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.958105ms 2023-05-18T12:15:26.41082+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:31.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.890805ms 2023-05-18T12:15:31.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:31.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.856922ms 2023-05-18T12:15:31.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:36.40364+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.308836ms 2023-05-18T12:15:36.40371+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:36.41038+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.292609ms 2023-05-18T12:15:36.41046+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:41.41008+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.096207ms 2023-05-18T12:15:41.41023+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.042925ms 2023-05-18T12:15:41.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:41.41029+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:46.4151+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.660115ms 2023-05-18T12:15:46.41518+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:46.42436+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.015219ms 2023-05-18T12:15:46.42441+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:46.45151+08:00 ERROR [539043,a68472eca9bbd280] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:15:51.41131+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.897004ms 2023-05-18T12:15:51.41137+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:51.41145+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.016438ms 2023-05-18T12:15:51.41148+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:56.41213+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.108907ms 2023-05-18T12:15:56.41219+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:15:56.41226+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.724847ms 2023-05-18T12:15:56.4123+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:01.40905+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.082999ms 2023-05-18T12:16:01.40912+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:01.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.6074ms 2023-05-18T12:16:01.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:06.41284+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.12262ms 2023-05-18T12:16:06.41291+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:06.41302+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.505258ms 2023-05-18T12:16:06.41305+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:11.41051+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.832303ms 2023-05-18T12:16:11.41059+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:11.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.855322ms 2023-05-18T12:16:11.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:16.40221+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.07762ms 2023-05-18T12:16:16.40228+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:16.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.976305ms 2023-05-18T12:16:16.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:16.41105+08:00 ERROR [539043,acf9bc7f6bfd2151] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:16:21.40878+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.1151ms 2023-05-18T12:16:21.40886+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:21.41271+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.757529ms 2023-05-18T12:16:21.41276+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:26.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.34051ms 2023-05-18T12:16:26.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:26.41087+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.299828ms 2023-05-18T12:16:26.4109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:31.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.213808ms 2023-05-18T12:16:31.41099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:31.41108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.42143ms 2023-05-18T12:16:31.41111+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:36.41084+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.654233ms 2023-05-18T12:16:36.4109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:36.41394+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.250422ms 2023-05-18T12:16:36.41399+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:41.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.627914ms 2023-05-18T12:16:41.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:41.41064+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.639533ms 2023-05-18T12:16:41.41068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:46.42827+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.238309ms 2023-05-18T12:16:46.42833+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:46.42838+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.536932ms 2023-05-18T12:16:46.42842+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:46.46311+08:00 ERROR [539043,360d1f2b7f394729] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:16:46.48132+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 1000532 fields:, error="open /proc/1000532/status: no such file or directory" 2023-05-18T12:16:46.48138+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 1000553 fields:, error="open /proc/1000553/status: no such file or directory" 2023-05-18T12:16:51.40837+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.036598ms 2023-05-18T12:16:51.40843+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:51.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.271509ms 2023-05-18T12:16:51.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:56.40313+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.135334ms 2023-05-18T12:16:56.40319+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:16:56.41004+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.979105ms 2023-05-18T12:16:56.41009+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:01.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.940205ms 2023-05-18T12:17:01.41083+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:01.41092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.183327ms 2023-05-18T12:17:01.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:06.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.29241ms 2023-05-18T12:17:06.41052+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:06.41061+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.250928ms 2023-05-18T12:17:06.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:11.41144+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.229308ms 2023-05-18T12:17:11.41153+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:11.41162+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.725534ms 2023-05-18T12:17:11.41166+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:16.40283+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.210021ms 2023-05-18T12:17:16.4029+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:16.41113+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.176508ms 2023-05-18T12:17:16.41117+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:16.4119+08:00 ERROR [539043,b9f40d30e3375a72] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:17:21.40182+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.860317ms 2023-05-18T12:17:21.40188+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:21.40879+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.172308ms 2023-05-18T12:17:21.40884+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:26.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.994806ms 2023-05-18T12:17:26.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:26.41064+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.903123ms 2023-05-18T12:17:26.41068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:31.40264+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.654628ms 2023-05-18T12:17:31.40272+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:31.40778+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.187508ms 2023-05-18T12:17:31.40783+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:36.41092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.429712ms 2023-05-18T12:17:36.41099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:36.41107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.701934ms 2023-05-18T12:17:36.4111+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:41.40873+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.253702ms 2023-05-18T12:17:41.40881+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:41.41168+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.211208ms 2023-05-18T12:17:41.41174+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:46.41545+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.006919ms 2023-05-18T12:17:46.41554+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:46.42375+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.091506ms 2023-05-18T12:17:46.42381+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:46.45145+08:00 ERROR [539043,b62e52ca8fc36ac9] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:17:51.41005+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.796503ms 2023-05-18T12:17:51.41012+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:51.4102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.798422ms 2023-05-18T12:17:51.41023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:56.40968+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.696602ms 2023-05-18T12:17:56.40975+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:17:56.40982+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.65432ms 2023-05-18T12:17:56.40985+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:01.41039+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.833603ms 2023-05-18T12:18:01.41046+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:01.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.023725ms 2023-05-18T12:18:01.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:06.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.514599ms 2023-05-18T12:18:06.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:06.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.601519ms 2023-05-18T12:18:06.41048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:11.41061+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.194608ms 2023-05-18T12:18:11.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:11.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.949724ms 2023-05-18T12:18:11.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:16.40289+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.901018ms 2023-05-18T12:18:16.40295+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:16.41116+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.180808ms 2023-05-18T12:18:16.41121+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:16.41188+08:00 ERROR [539043,200b03f59297e5af] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:18:21.41014+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.308109ms 2023-05-18T12:18:21.41021+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:21.41028+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.171827ms 2023-05-18T12:18:21.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:26.40314+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.133533ms 2023-05-18T12:18:26.40321+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:26.40998+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.235909ms 2023-05-18T12:18:26.41003+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:31.40611+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.739255ms 2023-05-18T12:18:31.40618+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:31.41488+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.658014ms 2023-05-18T12:18:31.41495+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:36.40259+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.906118ms 2023-05-18T12:18:36.40266+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:36.40853+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.158708ms 2023-05-18T12:18:36.40858+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:41.4022+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.935918ms 2023-05-18T12:18:41.40226+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:41.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.105507ms 2023-05-18T12:18:41.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:46.43509+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=27.372761ms 2023-05-18T12:18:46.43516+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:46.43526+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=27.046857ms 2023-05-18T12:18:46.43529+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:46.44867+08:00 ERROR [539043,e2ebab5ccc38b821] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:18:51.41004+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.109707ms 2023-05-18T12:18:51.41011+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:51.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.037725ms 2023-05-18T12:18:51.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:56.40213+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.11592ms 2023-05-18T12:18:56.40221+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:18:56.40873+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.122907ms 2023-05-18T12:18:56.40878+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:01.41136+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.196009ms 2023-05-18T12:19:01.41143+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:01.41152+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.784135ms 2023-05-18T12:19:01.41155+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:06.41083+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.128707ms 2023-05-18T12:19:06.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:06.41099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.210127ms 2023-05-18T12:19:06.41102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:11.41066+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.999806ms 2023-05-18T12:19:11.41073+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:11.4108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.964224ms 2023-05-18T12:19:11.41083+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:16.40415+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.262935ms 2023-05-18T12:19:16.40421+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:16.41246+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.202308ms 2023-05-18T12:19:16.41251+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:16.41371+08:00 ERROR [539043,ab44184218896293] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:19:21.41128+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.129907ms 2023-05-18T12:19:21.41137+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:21.41148+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.546032ms 2023-05-18T12:19:21.41151+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:26.41028+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.325309ms 2023-05-18T12:19:26.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:26.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.250928ms 2023-05-18T12:19:26.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:31.41267+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.506626ms 2023-05-18T12:19:31.41273+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:31.41281+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.951651ms 2023-05-18T12:19:31.41284+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:36.41016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.014606ms 2023-05-18T12:19:36.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:36.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.949424ms 2023-05-18T12:19:36.41033+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:41.40786+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=14.698495ms 2023-05-18T12:19:41.40792+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:41.40967+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.864803ms 2023-05-18T12:19:41.40972+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:46.43564+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=28.695279ms 2023-05-18T12:19:46.43571+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:46.43577+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=29.300687ms 2023-05-18T12:19:46.4358+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:46.45566+08:00 ERROR [539043,68783ef0e067f4e2] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:19:51.41101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.157707ms 2023-05-18T12:19:51.41107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:51.41116+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.364229ms 2023-05-18T12:19:51.4112+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:56.41036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.172707ms 2023-05-18T12:19:56.41043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:19:56.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.178127ms 2023-05-18T12:19:56.41055+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:01.41064+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.590614ms 2023-05-18T12:20:01.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:01.41081+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.623033ms 2023-05-18T12:20:01.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:06.41037+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.053006ms 2023-05-18T12:20:06.41043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:06.41051+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.709921ms 2023-05-18T12:20:06.41053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:11.40985+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.978206ms 2023-05-18T12:20:11.40991+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:11.40998+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.868322ms 2023-05-18T12:20:11.41001+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:16.40232+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.948218ms 2023-05-18T12:20:16.40239+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:16.41054+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.115207ms 2023-05-18T12:20:16.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:16.41133+08:00 ERROR [539043,2de7b7403d6b4268] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:20:16.43856+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields:, module=monitor.ob, duration="29.8µs" 2023-05-18T12:20:16.43865+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields:, module=monitor.ob, eventType=add, duration="7.9µs" 2023-05-18T12:20:16.43868+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields: duration="4.5µs", module=monitor.ob 2023-05-18T12:20:16.43872+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields: eventType=add, duration="4.3µs", module=monitor.ob 2023-05-18T12:20:16.43875+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T12:20:16.4463+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc0006c48c0 0xc0006c4960 0xc0006c4a00 0xc0006c4aa0 0xc0006c4b40 0xc0006c4be0 0xc0006c4c80 0xc0006c4d20 0xc0006c4dc0 0xc0006c4e60 0xc0006c4f00 0xc0006c4fa0 0xc0006c5040 0xc0006c50e0 0xc0006c5180 0xc0006c5220 0xc0006c52c0 0xc0006c5360 0xc0006c5400 0xc0006c54a0 0xc0006c5540 0xc0006c55e0 0xc0006c5680 0xc0006c5720 0xc0006c57c0 0xc0006c5860 0xc0006c5900 0xc0006c59a0 0xc0006c5a40 0xc0006c5ae0 0xc0006c5b80] CollectInterval:1s TimeAlign:false} 2023-05-18T12:20:16.44851+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T12:20:16.44857+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields: input=mysqlTableInput, duration="28µs" 2023-05-18T12:20:16.44861+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields: duration="71.701µs", input=mysqlTableInput 2023-05-18T12:20:16.44864+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields:, module=monitor.ob, eventType=add, error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)", duration=9.923031ms 2023-05-18T12:20:16.44866+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields: module=monitor.ob, eventType=add, duration=9.947532ms 2023-05-18T12:20:16.4487+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields:, module=monitor.ob, duration=10.024932ms 2023-05-18T12:20:16.44871+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields: eventType=add, duration=10.071033ms, module=monitor.ob 2023-05-18T12:20:16.44873+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields:, module=monitor.ob, duration=10.201035ms 2023-05-18T12:20:16.44876+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 11 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T12:20:21.40169+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.738315ms 2023-05-18T12:20:21.40175+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:21.40771+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.127608ms 2023-05-18T12:20:21.40776+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:26.40367+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.230635ms 2023-05-18T12:20:26.40373+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:26.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.137507ms 2023-05-18T12:20:26.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:31.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.138607ms 2023-05-18T12:20:31.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:31.41092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.170726ms 2023-05-18T12:20:31.41095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:36.4019+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.773116ms 2023-05-18T12:20:36.40196+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:36.40811+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.286409ms 2023-05-18T12:20:36.40817+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:41.40224+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.475112ms 2023-05-18T12:20:41.40232+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:41.40895+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.387211ms 2023-05-18T12:20:41.409+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:46.43205+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=27.524363ms 2023-05-18T12:20:46.43213+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:46.43228+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=27.139558ms 2023-05-18T12:20:46.43232+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:46.44564+08:00 ERROR [539043,2cb54a7481da19cb] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:20:51.40966+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.299915ms 2023-05-18T12:20:51.40973+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:51.41007+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.033706ms 2023-05-18T12:20:51.41012+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:56.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.965905ms 2023-05-18T12:20:56.4104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:20:56.41047+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.753821ms 2023-05-18T12:20:56.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:01.41196+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.063706ms 2023-05-18T12:21:01.41202+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:01.4121+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.533045ms 2023-05-18T12:21:01.41212+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:06.41066+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.272109ms 2023-05-18T12:21:06.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:06.41082+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.938524ms 2023-05-18T12:21:06.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:11.41004+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.072107ms 2023-05-18T12:21:11.41011+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:11.41018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.928724ms 2023-05-18T12:21:11.41021+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:16.40289+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.982218ms 2023-05-18T12:21:16.40296+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:16.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.915104ms 2023-05-18T12:21:16.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:16.41164+08:00 ERROR [539043,bf0475f35b734948] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:21:21.41135+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.378043ms 2023-05-18T12:21:21.41143+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:21.41193+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.424124ms 2023-05-18T12:21:21.41199+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:26.41112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.116007ms 2023-05-18T12:21:26.41118+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:26.41125+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.41863ms 2023-05-18T12:21:26.41128+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:31.41076+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.195608ms 2023-05-18T12:21:31.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:31.41094+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.058625ms 2023-05-18T12:21:31.41097+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:36.41026+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.183908ms 2023-05-18T12:21:36.41033+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:36.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.808622ms 2023-05-18T12:21:36.41044+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:41.40672+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.695368ms 2023-05-18T12:21:41.40679+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:41.41083+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.056106ms 2023-05-18T12:21:41.41088+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:46.41622+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.764616ms 2023-05-18T12:21:46.4163+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:46.43461+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.077307ms 2023-05-18T12:21:46.43466+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:46.4683+08:00 ERROR [539043,ddcec76cc7d0652f] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:21:51.41036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.214008ms 2023-05-18T12:21:51.41044+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:51.41054+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.42343ms 2023-05-18T12:21:51.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:56.41104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.267309ms 2023-05-18T12:21:56.41113+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:21:56.41122+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.313528ms 2023-05-18T12:21:56.41125+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:01.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.131407ms 2023-05-18T12:22:01.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:01.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.648233ms 2023-05-18T12:22:01.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:06.408+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.647193ms 2023-05-18T12:22:06.40806+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:06.41023+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.061607ms 2023-05-18T12:22:06.41028+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:11.40899+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.359603ms 2023-05-18T12:22:11.40907+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:11.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.153607ms 2023-05-18T12:22:11.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:16.40239+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.080519ms 2023-05-18T12:22:16.40245+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:16.41066+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.142208ms 2023-05-18T12:22:16.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:16.41135+08:00 ERROR [539043,85b8fcb00f996826] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:22:21.41064+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.244328ms 2023-05-18T12:22:21.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:21.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.615514ms 2023-05-18T12:22:21.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:26.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.182008ms 2023-05-18T12:22:26.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:26.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.249828ms 2023-05-18T12:22:26.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:31.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.909204ms 2023-05-18T12:22:31.4106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:31.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.010725ms 2023-05-18T12:22:31.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:36.40243+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.636214ms 2023-05-18T12:22:36.4025+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:36.40873+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.241409ms 2023-05-18T12:22:36.40878+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:41.41325+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.225454ms 2023-05-18T12:22:41.41333+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:41.41454+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.664941ms 2023-05-18T12:22:41.4146+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:46.40678+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.382424ms 2023-05-18T12:22:46.40684+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:46.41529+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.417912ms 2023-05-18T12:22:46.41535+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:46.46201+08:00 ERROR [539043,d63714aaacf88358] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:22:51.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.233109ms 2023-05-18T12:22:51.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:51.41065+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.966624ms 2023-05-18T12:22:51.41068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:56.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.197308ms 2023-05-18T12:22:56.4106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:22:56.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.44433ms 2023-05-18T12:22:56.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:01.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.110007ms 2023-05-18T12:23:01.41075+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:01.41082+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.413129ms 2023-05-18T12:23:01.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:06.40884+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.235501ms 2023-05-18T12:23:06.4089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:06.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.824603ms 2023-05-18T12:23:06.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:11.41159+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.280623ms 2023-05-18T12:23:11.41166+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:11.41176+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.15914ms 2023-05-18T12:23:11.41179+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:16.40286+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.047119ms 2023-05-18T12:23:16.40292+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:16.4111+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.134907ms 2023-05-18T12:23:16.41114+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:16.4118+08:00 ERROR [539043,0c089cc508e71e4e] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:23:21.41176+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.312609ms 2023-05-18T12:23:21.41185+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:21.41193+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.948537ms 2023-05-18T12:23:21.41197+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:26.40753+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.519291ms 2023-05-18T12:23:26.40761+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:26.41174+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.616714ms 2023-05-18T12:23:26.41178+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:31.40643+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.458777ms 2023-05-18T12:23:31.4065+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:31.40994+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.960005ms 2023-05-18T12:23:31.41+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:36.40814+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.504392ms 2023-05-18T12:23:36.40822+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:36.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.845203ms 2023-05-18T12:23:36.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:41.4101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.943505ms 2023-05-18T12:23:41.41016+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:41.41023+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.808322ms 2023-05-18T12:23:41.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:46.43421+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=26.910655ms 2023-05-18T12:23:46.43429+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:46.43434+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.52675ms 2023-05-18T12:23:46.43437+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:46.45315+08:00 ERROR [539043,8de186255e8cb97a] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:23:51.41207+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.604526ms 2023-05-18T12:23:51.41213+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:51.4122+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.252141ms 2023-05-18T12:23:51.41224+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:56.40189+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.650114ms 2023-05-18T12:23:56.40197+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:23:56.40792+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.066906ms 2023-05-18T12:23:56.40796+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:01.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.916605ms 2023-05-18T12:24:01.41075+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:01.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.147027ms 2023-05-18T12:24:01.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:06.41008+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.788303ms 2023-05-18T12:24:06.41015+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:06.41022+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.836522ms 2023-05-18T12:24:06.41025+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:11.41071+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.078206ms 2023-05-18T12:24:11.41077+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:11.41084+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.809222ms 2023-05-18T12:24:11.41087+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:16.40183+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.693615ms 2023-05-18T12:24:16.40191+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:16.40956+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.610201ms 2023-05-18T12:24:16.40962+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:16.41045+08:00 ERROR [539043,bf875cdc71d67c26] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:24:21.40666+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.474778ms 2023-05-18T12:24:21.40674+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:21.40937+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.665001ms 2023-05-18T12:24:21.40943+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:26.40953+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.594501ms 2023-05-18T12:24:26.40962+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:26.40974+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.532218ms 2023-05-18T12:24:26.40977+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:31.40169+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.730716ms 2023-05-18T12:24:31.40176+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:31.40765+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.085206ms 2023-05-18T12:24:31.4077+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:36.41125+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.341229ms 2023-05-18T12:24:36.41132+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:36.41137+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.414411ms 2023-05-18T12:24:36.4114+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:41.41111+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.891604ms 2023-05-18T12:24:41.41119+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:41.41126+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.229127ms 2023-05-18T12:24:41.4113+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:46.42516+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.72672ms 2023-05-18T12:24:46.42523+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:46.42529+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.353829ms 2023-05-18T12:24:46.42532+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:46.45572+08:00 ERROR [539043,21d4a544e1f5af52] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:24:51.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.867504ms 2023-05-18T12:24:51.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:51.4107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.71682ms 2023-05-18T12:24:51.41073+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:56.40978+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.815204ms 2023-05-18T12:24:56.40984+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:24:56.40991+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.70092ms 2023-05-18T12:24:56.40993+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:01.41051+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.986105ms 2023-05-18T12:25:01.41059+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:01.41066+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.843722ms 2023-05-18T12:25:01.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:06.41037+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.947505ms 2023-05-18T12:25:06.41068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:06.41115+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.880836ms 2023-05-18T12:25:06.41119+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:11.40491+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.307049ms 2023-05-18T12:25:11.40498+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:11.41012+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.721202ms 2023-05-18T12:25:11.41018+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:16.40164+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.390411ms 2023-05-18T12:25:16.4017+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:16.40175+08:00 ERROR [539043,24641bbdd297fd3c] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:25:16.40793+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.086107ms 2023-05-18T12:25:16.40798+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:21.41205+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.991406ms 2023-05-18T12:25:21.41212+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:21.41221+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.596645ms 2023-05-18T12:25:21.41224+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:26.40966+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.792903ms 2023-05-18T12:25:26.40973+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:26.4098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.480718ms 2023-05-18T12:25:26.40982+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:31.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.071406ms 2023-05-18T12:25:31.41083+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:31.41095+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.286129ms 2023-05-18T12:25:31.41098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:36.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.282609ms 2023-05-18T12:25:36.4104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:36.41048+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.315229ms 2023-05-18T12:25:36.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:41.41005+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.855104ms 2023-05-18T12:25:41.41011+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:41.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.725221ms 2023-05-18T12:25:41.41025+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:46.41675+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.916017ms 2023-05-18T12:25:46.41682+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:46.42497+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.068307ms 2023-05-18T12:25:46.42501+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:46.45676+08:00 ERROR [539043,dfa1ee4f57849aa0] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:25:51.40184+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.836517ms 2023-05-18T12:25:51.4019+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:51.40777+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.155707ms 2023-05-18T12:25:51.40782+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:56.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.649501ms 2023-05-18T12:25:56.41033+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:25:56.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.684421ms 2023-05-18T12:25:56.41045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:01.40695+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.562479ms 2023-05-18T12:26:01.40701+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:01.40982+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.667002ms 2023-05-18T12:26:01.40988+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:06.41186+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.012206ms 2023-05-18T12:26:06.41193+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:06.41202+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.318442ms 2023-05-18T12:26:06.41206+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:11.41014+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.063506ms 2023-05-18T12:26:11.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:11.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.195627ms 2023-05-18T12:26:11.41033+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:16.40313+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.505625ms 2023-05-18T12:26:16.4032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:16.41133+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.090307ms 2023-05-18T12:26:16.41138+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:16.41206+08:00 ERROR [539043,9eee55f9950bb227] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:26:21.40647+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.329976ms 2023-05-18T12:26:21.40653+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:21.41156+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.897217ms 2023-05-18T12:26:21.41162+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:26.41003+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.153908ms 2023-05-18T12:26:26.41009+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:26.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.016324ms 2023-05-18T12:26:26.4102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:31.40311+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.107033ms 2023-05-18T12:26:31.40317+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:31.40969+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.107007ms 2023-05-18T12:26:31.40975+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:36.4107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.966805ms 2023-05-18T12:26:36.41076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:36.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.332029ms 2023-05-18T12:26:36.4109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:41.4081+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=14.546092ms 2023-05-18T12:26:41.40816+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:41.40963+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.5745ms 2023-05-18T12:26:41.40968+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:46.43219+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=25.375035ms 2023-05-18T12:26:46.43225+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:46.43231+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=25.964642ms 2023-05-18T12:26:46.43234+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:46.45412+08:00 ERROR [539043,2907f0aec1135e41] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:26:46.46495+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 1068920 fields: error="open /proc/1068920/status: no such file or directory" 2023-05-18T12:26:46.465+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 1068937 fields:, error="open /proc/1068937/status: no such file or directory" 2023-05-18T12:26:51.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.342029ms 2023-05-18T12:26:51.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:51.41117+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.736502ms 2023-05-18T12:26:51.41121+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:56.4101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.762002ms 2023-05-18T12:26:56.41017+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:26:56.41025+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.571518ms 2023-05-18T12:26:56.41029+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:01.40975+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.095412ms 2023-05-18T12:27:01.40981+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:01.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.182608ms 2023-05-18T12:27:01.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:06.4109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.045806ms 2023-05-18T12:27:06.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:06.41103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.505131ms 2023-05-18T12:27:06.41106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:11.41025+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.656801ms 2023-05-18T12:27:11.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:11.41039+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.414516ms 2023-05-18T12:27:11.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:16.40246+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.942018ms 2023-05-18T12:27:16.40252+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:16.41038+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.813503ms 2023-05-18T12:27:16.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:16.41108+08:00 ERROR [539043,eaacf377ef8b1eb6] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:27:21.41149+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.952805ms 2023-05-18T12:27:21.41155+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:21.41166+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.656933ms 2023-05-18T12:27:21.4117+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:26.40576+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.262762ms 2023-05-18T12:27:26.40583+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:26.41022+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.046506ms 2023-05-18T12:27:26.41028+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:31.40296+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.181121ms 2023-05-18T12:27:31.40304+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:31.40883+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.280509ms 2023-05-18T12:27:31.40888+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:36.40191+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.806017ms 2023-05-18T12:27:36.40198+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:36.40986+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.848403ms 2023-05-18T12:27:36.4099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:41.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.560918ms 2023-05-18T12:27:41.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:41.4107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.057506ms 2023-05-18T12:27:41.41073+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:46.41291+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.781595ms 2023-05-18T12:27:46.41297+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:46.4316+08:00 ERROR [539043,4012b0fcf5bb2683] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:27:46.43176+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=27.112658ms 2023-05-18T12:27:46.43181+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:51.41117+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.127008ms 2023-05-18T12:27:51.41124+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:51.41133+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.330929ms 2023-05-18T12:27:51.41137+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:56.41001+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.266015ms 2023-05-18T12:27:56.41011+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:27:56.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.440411ms 2023-05-18T12:27:56.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:01.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.144307ms 2023-05-18T12:28:01.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:01.41059+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.114426ms 2023-05-18T12:28:01.41063+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:06.40955+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.707001ms 2023-05-18T12:28:06.40962+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:06.40971+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.478017ms 2023-05-18T12:28:06.40974+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:11.41016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.756502ms 2023-05-18T12:28:11.41023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:11.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.409817ms 2023-05-18T12:28:11.41034+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:16.40266+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.233122ms 2023-05-18T12:28:16.40273+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:16.41098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.217808ms 2023-05-18T12:28:16.41104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:16.41219+08:00 ERROR [539043,9389e2194e7a1771] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:28:21.40977+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.749902ms 2023-05-18T12:28:21.40983+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:21.40991+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.69322ms 2023-05-18T12:28:21.40995+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:26.4026+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.298623ms 2023-05-18T12:28:26.40269+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:26.40795+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.019406ms 2023-05-18T12:28:26.408+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:31.40452+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.070546ms 2023-05-18T12:28:31.4046+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:31.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.069407ms 2023-05-18T12:28:31.41068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:36.40977+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.697602ms 2023-05-18T12:28:36.40984+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:36.40994+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.771121ms 2023-05-18T12:28:36.40997+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:41.40229+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.814116ms 2023-05-18T12:28:41.40235+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:41.40998+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.602801ms 2023-05-18T12:28:41.41003+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:46.42535+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.763516ms 2023-05-18T12:28:46.42542+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:46.42561+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.081138ms 2023-05-18T12:28:46.42565+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:46.46696+08:00 ERROR [539043,5b50166403b40084] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:28:51.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.218509ms 2023-05-18T12:28:51.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:51.41103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.153127ms 2023-05-18T12:28:51.41108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:56.41136+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.840117ms 2023-05-18T12:28:56.41144+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:28:56.41152+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.009538ms 2023-05-18T12:28:56.41156+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:01.41384+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=20.650473ms 2023-05-18T12:29:01.4139+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:01.41611+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.293149ms 2023-05-18T12:29:01.41616+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:06.41178+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.024119ms 2023-05-18T12:29:06.41184+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:06.41191+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.121639ms 2023-05-18T12:29:06.41195+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:11.40969+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.774209ms 2023-05-18T12:29:11.40975+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:11.4111+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.198108ms 2023-05-18T12:29:11.41115+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:16.40238+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.08532ms 2023-05-18T12:29:16.40247+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:16.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.139807ms 2023-05-18T12:29:16.41075+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:16.41149+08:00 ERROR [539043,a4c71ba72de8ec01] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:29:21.41166+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.908337ms 2023-05-18T12:29:21.41173+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:21.41178+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.838016ms 2023-05-18T12:29:21.41181+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:26.40955+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.657901ms 2023-05-18T12:29:26.40965+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:26.40974+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.574719ms 2023-05-18T12:29:26.40977+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:31.40987+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.893905ms 2023-05-18T12:29:31.40993+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:31.41+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.875222ms 2023-05-18T12:29:31.41004+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:36.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.245309ms 2023-05-18T12:29:36.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:36.41047+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.322329ms 2023-05-18T12:29:36.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:41.40173+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.772515ms 2023-05-18T12:29:41.40179+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:41.40963+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.006819ms 2023-05-18T12:29:41.40968+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:46.41649+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.729415ms 2023-05-18T12:29:46.41656+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:46.42528+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.629614ms 2023-05-18T12:29:46.42533+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:46.45009+08:00 ERROR [539043,fd15f6d082ea9481] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:29:51.40997+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.916704ms 2023-05-18T12:29:51.41004+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:51.41013+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.924223ms 2023-05-18T12:29:51.41016+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:56.40552+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.841856ms 2023-05-18T12:29:56.40561+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:29:56.41+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.785302ms 2023-05-18T12:29:56.41005+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:01.40978+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.746897ms 2023-05-18T12:30:01.40984+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:01.40992+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.498405ms 2023-05-18T12:30:01.40995+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:06.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.082001ms 2023-05-18T12:30:06.41027+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:06.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.919311ms 2023-05-18T12:30:06.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:11.41051+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.107401ms 2023-05-18T12:30:11.41059+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:11.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.88771ms 2023-05-18T12:30:11.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:16.40259+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.060013ms 2023-05-18T12:30:16.40266+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:16.41078+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.081101ms 2023-05-18T12:30:16.41083+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:16.41141+08:00 ERROR [539043,364cba4006b653fb] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:30:16.44979+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields:, module=monitor.ob, duration="18.3µs" 2023-05-18T12:30:16.44985+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields:, module=monitor.ob, eventType=add, duration="4.9µs" 2023-05-18T12:30:16.44988+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields: module=monitor.ob, duration="4.2µs" 2023-05-18T12:30:16.44991+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields:, module=monitor.ob, eventType=add, duration="4.6µs" 2023-05-18T12:30:16.44994+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T12:30:16.45645+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc00086caa0 0xc00086cb40 0xc00086cbe0 0xc00086cc80 0xc00086cd20 0xc00086cdc0 0xc00086ce60 0xc00086cf00 0xc00086cfa0 0xc00086d040 0xc00086d0e0 0xc00086d180 0xc00086d220 0xc00086d2c0 0xc00086d360 0xc00086d400 0xc00086d4a0 0xc00086d540 0xc00086d5e0 0xc00086d680 0xc00086d720 0xc00086d7c0 0xc00086d860 0xc00086d900 0xc00086d9a0 0xc00086da40 0xc00086dae0 0xc00086db80 0xc00086dc20 0xc00086dcc0 0xc00086dd60] CollectInterval:1s TimeAlign:false} 2023-05-18T12:30:16.45912+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T12:30:16.45915+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields:, input=mysqlTableInput, duration="4.8µs" 2023-05-18T12:30:16.45917+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields:, input=mysqlTableInput, duration="23.9µs" 2023-05-18T12:30:16.45919+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields: error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)", duration=9.277915ms, module=monitor.ob, eventType=add 2023-05-18T12:30:16.45921+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields:, module=monitor.ob, eventType=add, duration=9.296215ms 2023-05-18T12:30:16.45922+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields: module=monitor.ob, duration=9.351217ms 2023-05-18T12:30:16.45924+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields:, module=monitor.ob, eventType=add, duration=9.391617ms 2023-05-18T12:30:16.45925+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields: module=monitor.ob, duration=9.475418ms 2023-05-18T12:30:16.45928+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 12 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T12:30:21.40545+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.23974ms 2023-05-18T12:30:21.40551+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:21.41354+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.9844ms 2023-05-18T12:30:21.4136+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:26.41097+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.883398ms 2023-05-18T12:30:26.41128+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:26.41175+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.718621ms 2023-05-18T12:30:26.41179+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:31.41018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.995ms 2023-05-18T12:30:31.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:31.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.798909ms 2023-05-18T12:30:31.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:36.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.898898ms 2023-05-18T12:30:36.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:36.4107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.772409ms 2023-05-18T12:30:36.41073+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:41.40216+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.670308ms 2023-05-18T12:30:41.40223+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:41.40816+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.055801ms 2023-05-18T12:30:41.4082+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:46.43468+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.367229ms 2023-05-18T12:30:46.43475+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:46.4348+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=27.048837ms 2023-05-18T12:30:46.43483+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:46.44882+08:00 ERROR [539043,7d7226646174df85] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:30:51.41131+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.753409ms 2023-05-18T12:30:51.41138+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:51.41145+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.514018ms 2023-05-18T12:30:51.41148+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:56.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.0484ms 2023-05-18T12:30:56.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:30:56.41093+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.038012ms 2023-05-18T12:30:56.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:01.41018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.987899ms 2023-05-18T12:31:01.41025+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:01.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.812009ms 2023-05-18T12:31:01.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:06.40986+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.925599ms 2023-05-18T12:31:06.40992+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:06.41002+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.911811ms 2023-05-18T12:31:06.41005+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:11.40325+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.271828ms 2023-05-18T12:31:11.40332+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:11.40787+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.244403ms 2023-05-18T12:31:11.40793+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:16.40271+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.028412ms 2023-05-18T12:31:16.40279+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:16.41065+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.821297ms 2023-05-18T12:31:16.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:16.41142+08:00 ERROR [539043,845a4fb9dd998f77] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:31:21.41164+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.308116ms 2023-05-18T12:31:21.41171+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:21.41178+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.44283ms 2023-05-18T12:31:21.41181+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:26.40883+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.176989ms 2023-05-18T12:31:26.40889+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:26.41222+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.293415ms 2023-05-18T12:31:26.4126+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:31.40283+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.844223ms 2023-05-18T12:31:31.40289+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:31.40806+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.308304ms 2023-05-18T12:31:31.40811+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:36.40189+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.389604ms 2023-05-18T12:31:36.40197+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:36.40954+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.534994ms 2023-05-18T12:31:36.4096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:41.41+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.695408ms 2023-05-18T12:31:41.41008+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:41.41022+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.156101ms 2023-05-18T12:31:41.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:46.41752+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=21.200164ms 2023-05-18T12:31:46.4176+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:46.41771+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.704196ms 2023-05-18T12:31:46.41775+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:46.43908+08:00 ERROR [539043,ceab545da9c50dab] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:31:51.41004+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.243403ms 2023-05-18T12:31:51.41013+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:51.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.013112ms 2023-05-18T12:31:51.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:56.41082+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.615908ms 2023-05-18T12:31:56.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:31:56.41101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.610819ms 2023-05-18T12:31:56.41105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:01.4116+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.85311ms 2023-05-18T12:32:01.41167+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:01.41176+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.790122ms 2023-05-18T12:32:01.41179+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:06.40707+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.058663ms 2023-05-18T12:32:06.40714+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:06.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.853597ms 2023-05-18T12:32:06.41054+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:11.41112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.241503ms 2023-05-18T12:32:11.4112+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:11.41128+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.821823ms 2023-05-18T12:32:11.41131+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:16.4027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.960512ms 2023-05-18T12:32:16.40276+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:16.411+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.195302ms 2023-05-18T12:32:16.41105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:16.41172+08:00 ERROR [539043,8b04ad32d444d70d] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:32:21.40263+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.983112ms 2023-05-18T12:32:21.40269+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:21.40857+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.238503ms 2023-05-18T12:32:21.40864+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:26.4025+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.269815ms 2023-05-18T12:32:26.40256+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:26.41071+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.100501ms 2023-05-18T12:32:26.41076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:31.40973+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.532006ms 2023-05-18T12:32:31.40979+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:31.4099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.170402ms 2023-05-18T12:32:31.40993+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:36.41113+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.82941ms 2023-05-18T12:32:36.4112+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:36.41128+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.544419ms 2023-05-18T12:32:36.41132+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:41.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.217503ms 2023-05-18T12:32:41.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:41.41065+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.448418ms 2023-05-18T12:32:41.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:46.43393+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=26.52103ms 2023-05-18T12:32:46.43399+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:46.43413+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=31.415892ms 2023-05-18T12:32:46.43416+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:46.45516+08:00 ERROR [539043,e58925f8153e564c] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:32:51.40565+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.492743ms 2023-05-18T12:32:51.40572+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:51.41378+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.0132ms 2023-05-18T12:32:51.41382+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:56.41078+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.381804ms 2023-05-18T12:32:56.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:32:56.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.260815ms 2023-05-18T12:32:56.41094+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:01.41222+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.342203ms 2023-05-18T12:33:01.41228+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:01.41236+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.883935ms 2023-05-18T12:33:01.41239+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:06.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.167302ms 2023-05-18T12:33:06.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:06.411+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.286116ms 2023-05-18T12:33:06.41104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:11.411+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.261803ms 2023-05-18T12:33:11.41106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:11.41115+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.353316ms 2023-05-18T12:33:11.41119+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:16.40221+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.031913ms 2023-05-18T12:33:16.40227+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:16.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.183702ms 2023-05-18T12:33:16.41054+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:16.41118+08:00 ERROR [539043,58b30e3d0d7038a2] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:33:21.4031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.103126ms 2023-05-18T12:33:21.40317+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:21.41002+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.988599ms 2023-05-18T12:33:21.41007+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:26.41048+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.809597ms 2023-05-18T12:33:26.41055+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:26.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.973811ms 2023-05-18T12:33:26.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:31.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.991799ms 2023-05-18T12:33:31.41066+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:31.41075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.068513ms 2023-05-18T12:33:31.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:36.41076+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.898199ms 2023-05-18T12:33:36.41083+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:36.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.954311ms 2023-05-18T12:33:36.41095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:41.40254+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.955511ms 2023-05-18T12:33:41.40269+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:41.40828+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.092001ms 2023-05-18T12:33:41.40834+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:46.43168+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=24.781209ms 2023-05-18T12:33:46.43174+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:46.43179+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=25.440217ms 2023-05-18T12:33:46.43181+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:46.43186+08:00 ERROR [539043,4b77346f01d65ad8] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:33:51.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.135001ms 2023-05-18T12:33:51.41098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:51.41107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.533318ms 2023-05-18T12:33:51.4111+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:56.41265+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.522806ms 2023-05-18T12:33:56.41271+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:33:56.41278+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.970236ms 2023-05-18T12:33:56.41283+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:01.4096+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.492994ms 2023-05-18T12:34:01.40968+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:01.40978+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.440505ms 2023-05-18T12:34:01.40982+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:06.41165+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.213415ms 2023-05-18T12:34:06.41199+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:06.41247+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.913736ms 2023-05-18T12:34:06.41251+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:11.40928+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.583494ms 2023-05-18T12:34:11.40934+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:11.40942+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.260803ms 2023-05-18T12:34:11.40945+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:16.40305+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.60142ms 2023-05-18T12:34:16.40311+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:16.41155+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.411605ms 2023-05-18T12:34:16.41162+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:16.41231+08:00 ERROR [539043,92d9cc6e010c7a6a] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:34:21.40856+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.437692ms 2023-05-18T12:34:21.40864+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:21.41038+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.274303ms 2023-05-18T12:34:21.41043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:26.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.757097ms 2023-05-18T12:34:26.41053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:26.41065+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.684908ms 2023-05-18T12:34:26.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:31.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.181902ms 2023-05-18T12:34:31.41059+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:31.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.108213ms 2023-05-18T12:34:31.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:36.40529+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.447142ms 2023-05-18T12:34:36.40536+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:36.41357+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.163101ms 2023-05-18T12:34:36.41363+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:41.41081+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.930799ms 2023-05-18T12:34:41.41088+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:41.41095+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.144214ms 2023-05-18T12:34:41.41098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:46.43487+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.684433ms 2023-05-18T12:34:46.43494+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:46.43499+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=27.24454ms 2023-05-18T12:34:46.43501+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:46.45592+08:00 ERROR [539043,81b6198bc43baee4] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:34:51.40183+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.622207ms 2023-05-18T12:34:51.4019+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:51.4079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.0404ms 2023-05-18T12:34:51.40796+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:56.41129+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.217702ms 2023-05-18T12:34:56.41137+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:34:56.41144+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.598819ms 2023-05-18T12:34:56.41148+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:01.40619+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.375054ms 2023-05-18T12:35:01.40626+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:01.41009+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.653996ms 2023-05-18T12:35:01.41015+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:06.41065+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.138902ms 2023-05-18T12:35:06.41073+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:06.4108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.229015ms 2023-05-18T12:35:06.41083+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:11.40154+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.580507ms 2023-05-18T12:35:11.40162+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:11.40829+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.636708ms 2023-05-18T12:35:11.40834+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:16.40289+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.192615ms 2023-05-18T12:35:16.40297+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:16.41095+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.942099ms 2023-05-18T12:35:16.411+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:16.41197+08:00 ERROR [539043,725247f631629001] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:35:21.40333+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.343517ms 2023-05-18T12:35:21.40339+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:21.40775+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.120902ms 2023-05-18T12:35:21.4078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:26.41087+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.092001ms 2023-05-18T12:35:26.41093+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:26.41102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.065513ms 2023-05-18T12:35:26.41105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:31.40594+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.449543ms 2023-05-18T12:35:31.40617+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:31.41504+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.734909ms 2023-05-18T12:35:31.4151+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:36.40261+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.658808ms 2023-05-18T12:35:36.40268+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:36.40892+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.430905ms 2023-05-18T12:35:36.40898+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:41.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.248103ms 2023-05-18T12:35:41.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:41.41074+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.055912ms 2023-05-18T12:35:41.41077+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:46.43422+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.661232ms 2023-05-18T12:35:46.43428+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:46.43435+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.271028ms 2023-05-18T12:35:46.43438+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:46.44832+08:00 ERROR [539043,f91118f83a70b3e7] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:35:51.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.0406ms 2023-05-18T12:35:51.41065+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:51.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.750909ms 2023-05-18T12:35:51.41076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:56.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.031ms 2023-05-18T12:35:56.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:35:56.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.127813ms 2023-05-18T12:35:56.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:01.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.893598ms 2023-05-18T12:36:01.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:01.41047+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.033812ms 2023-05-18T12:36:01.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:06.41006+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.0928ms 2023-05-18T12:36:06.41012+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:06.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.029912ms 2023-05-18T12:36:06.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:11.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.180102ms 2023-05-18T12:36:11.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:11.41097+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.263015ms 2023-05-18T12:36:11.411+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:16.40518+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.467643ms 2023-05-18T12:36:16.40525+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:16.41379+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.500605ms 2023-05-18T12:36:16.41384+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:16.41483+08:00 ERROR [539043,d3fd1df65abfe6e3] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:36:21.40394+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.245928ms 2023-05-18T12:36:21.404+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:21.41114+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.438905ms 2023-05-18T12:36:21.41119+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:26.41075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.108001ms 2023-05-18T12:36:26.41082+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:26.4109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.223915ms 2023-05-18T12:36:26.41093+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:31.40652+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.82146ms 2023-05-18T12:36:31.40659+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:31.41526+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.626108ms 2023-05-18T12:36:31.41532+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:36.41016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.148902ms 2023-05-18T12:36:36.41023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:36.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.053112ms 2023-05-18T12:36:36.41034+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:41.40996+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.654495ms 2023-05-18T12:36:41.41002+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:41.4101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.84441ms 2023-05-18T12:36:41.41013+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:46.4216+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.602607ms 2023-05-18T12:36:46.42166+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:46.42171+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.841147ms 2023-05-18T12:36:46.42174+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:46.45608+08:00 ERROR [539043,133460a729222a2f] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:36:51.40766+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=14.252677ms 2023-05-18T12:36:51.40772+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:51.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.157502ms 2023-05-18T12:36:51.4104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:56.40998+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.784597ms 2023-05-18T12:36:56.41004+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:36:56.41012+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.808009ms 2023-05-18T12:36:56.41015+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:01.4093+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.787698ms 2023-05-18T12:37:01.40937+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:01.40944+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.345003ms 2023-05-18T12:37:01.40947+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:06.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.072901ms 2023-05-18T12:37:06.41097+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:06.41104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.084012ms 2023-05-18T12:37:06.41107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:11.40207+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.696708ms 2023-05-18T12:37:11.40213+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:11.40831+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.188402ms 2023-05-18T12:37:11.40837+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:16.40199+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.84801ms 2023-05-18T12:37:16.40207+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:16.40988+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.764997ms 2023-05-18T12:37:16.40992+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:16.41063+08:00 ERROR [539043,066fe5489e34ef2d] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:37:21.40229+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.976711ms 2023-05-18T12:37:21.40236+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:21.41019+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.787297ms 2023-05-18T12:37:21.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:26.40365+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.528631ms 2023-05-18T12:37:26.40372+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:26.41015+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.199703ms 2023-05-18T12:37:26.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:31.41066+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.156001ms 2023-05-18T12:37:31.41073+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:31.41082+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.075513ms 2023-05-18T12:37:31.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:36.40986+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.928699ms 2023-05-18T12:37:36.40994+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:36.41002+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.80651ms 2023-05-18T12:37:36.41005+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:41.40957+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.693696ms 2023-05-18T12:37:41.40965+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:41.40973+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.548606ms 2023-05-18T12:37:41.40976+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:46.40706+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.923811ms 2023-05-18T12:37:46.40712+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:46.41483+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.672495ms 2023-05-18T12:37:46.41488+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:46.46305+08:00 ERROR [539043,5f88ea2d645074f1] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:37:51.40362+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.42363ms 2023-05-18T12:37:51.40369+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:51.41007+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.0476ms 2023-05-18T12:37:51.41013+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:56.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.213902ms 2023-05-18T12:37:56.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:37:56.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.759609ms 2023-05-18T12:37:56.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:01.41092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.234303ms 2023-05-18T12:38:01.41099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:01.41106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.054012ms 2023-05-18T12:38:01.41109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:06.41115+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.492906ms 2023-05-18T12:38:06.41122+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:06.4117+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.757322ms 2023-05-18T12:38:06.41175+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:11.41108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.533406ms 2023-05-18T12:38:11.41115+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:11.41125+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.411517ms 2023-05-18T12:38:11.41128+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:16.40259+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.324217ms 2023-05-18T12:38:16.40265+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:16.41074+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.0405ms 2023-05-18T12:38:16.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:16.41149+08:00 ERROR [539043,43d49bf452a45076] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:38:21.41047+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.0515ms 2023-05-18T12:38:21.41054+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:21.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.238515ms 2023-05-18T12:38:21.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:26.4102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.281603ms 2023-05-18T12:38:26.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:26.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.138914ms 2023-05-18T12:38:26.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:31.40635+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.973661ms 2023-05-18T12:38:31.40641+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:31.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.899999ms 2023-05-18T12:38:31.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:36.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.894298ms 2023-05-18T12:38:36.41086+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:36.41096+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.086113ms 2023-05-18T12:38:36.41099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:41.40308+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.183314ms 2023-05-18T12:38:41.40314+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:41.4091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.531306ms 2023-05-18T12:38:41.40915+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:46.4167+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.88741ms 2023-05-18T12:38:46.41676+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:46.42485+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.0127ms 2023-05-18T12:38:46.42489+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:46.4568+08:00 ERROR [539043,150f2a1adf32558a] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:38:51.41095+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.445605ms 2023-05-18T12:38:51.41101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:51.41109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.896811ms 2023-05-18T12:38:51.41115+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:56.41213+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.150414ms 2023-05-18T12:38:56.4122+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:38:56.41228+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.491131ms 2023-05-18T12:38:56.41231+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:01.41054+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.939199ms 2023-05-18T12:39:01.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:01.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.396117ms 2023-05-18T12:39:01.41077+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:06.41321+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.845947ms 2023-05-18T12:39:06.41327+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:06.41339+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.582007ms 2023-05-18T12:39:06.41343+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:11.40229+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.288615ms 2023-05-18T12:39:11.40236+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:11.40951+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.791522ms 2023-05-18T12:39:11.40957+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:16.40285+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.263216ms 2023-05-18T12:39:16.40292+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:16.41103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.076201ms 2023-05-18T12:39:16.41109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:16.41174+08:00 ERROR [539043,5d3eef9accb437ba] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:39:21.4108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.0193ms 2023-05-18T12:39:21.41087+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:21.41095+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.121913ms 2023-05-18T12:39:21.41098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:26.40271+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.79151ms 2023-05-18T12:39:26.40279+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:26.40913+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.563107ms 2023-05-18T12:39:26.40921+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:31.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.212702ms 2023-05-18T12:39:31.41058+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:31.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.087113ms 2023-05-18T12:39:31.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:36.41066+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.099401ms 2023-05-18T12:39:36.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:36.41081+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.116613ms 2023-05-18T12:39:36.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:41.41111+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.478105ms 2023-05-18T12:39:41.41117+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:41.41124+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.64392ms 2023-05-18T12:39:41.41127+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:46.41862+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.773297ms 2023-05-18T12:39:46.41869+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:46.41879+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.239327ms 2023-05-18T12:39:46.41885+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:46.44493+08:00 ERROR [539043,ac6e5adf3cd995b3] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:39:51.40661+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.716559ms 2023-05-18T12:39:51.40669+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:51.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.795797ms 2023-05-18T12:39:51.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:56.40941+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.609795ms 2023-05-18T12:39:56.40948+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:39:56.40955+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.318604ms 2023-05-18T12:39:56.4096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:01.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.322004ms 2023-05-18T12:40:01.41098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:01.41106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.357016ms 2023-05-18T12:40:01.41109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:06.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.9972ms 2023-05-18T12:40:06.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:06.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.202315ms 2023-05-18T12:40:06.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:11.41115+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.545307ms 2023-05-18T12:40:11.41121+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:11.41129+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.609219ms 2023-05-18T12:40:11.41132+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:16.40231+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.78011ms 2023-05-18T12:40:16.40239+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:16.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.085701ms 2023-05-18T12:40:16.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:16.41127+08:00 ERROR [539043,49bf131919f8517a] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:40:16.45967+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields: module=monitor.ob, duration="21.301µs" 2023-05-18T12:40:16.45975+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields:, module=monitor.ob, eventType=add, duration="7.8µs" 2023-05-18T12:40:16.45978+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields: module=monitor.ob, duration="6.7µs" 2023-05-18T12:40:16.45982+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields: eventType=add, duration="5.3µs", module=monitor.ob 2023-05-18T12:40:16.45985+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T12:40:16.46361+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc0002a8640 0xc0002a86e0 0xc0002a8780 0xc0002a8820 0xc0002a88c0 0xc0002a8960 0xc0002a8a00 0xc0002a8aa0 0xc0002a8b40 0xc0002a8be0 0xc0002a8c80 0xc0002a8d20 0xc0002a8dc0 0xc0002a8e60 0xc0002a8f00 0xc0002a8fa0 0xc0002a9040 0xc0002a90e0 0xc0002a9180 0xc0002a9220 0xc0002a92c0 0xc0002a9360 0xc0002a9400 0xc0002a94a0 0xc0002a9540 0xc0002a95e0 0xc0002a9680 0xc0002a9720 0xc0002a97c0 0xc0002a9860 0xc0002a9900] CollectInterval:1s TimeAlign:false} 2023-05-18T12:40:16.46446+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T12:40:16.46449+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields: input=mysqlTableInput, duration="6.7µs" 2023-05-18T12:40:16.46451+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields:, input=mysqlTableInput, duration="26.6µs" 2023-05-18T12:40:16.46454+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields: duration=4.723459ms, module=monitor.ob, eventType=add, error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:40:16.46456+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields:, module=monitor.ob, eventType=add, duration=4.74446ms 2023-05-18T12:40:16.46459+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields:, module=monitor.ob, duration=4.82416ms 2023-05-18T12:40:16.46462+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields: module=monitor.ob, eventType=add, duration=4.87496ms 2023-05-18T12:40:16.46463+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields: module=monitor.ob, duration=4.978562ms 2023-05-18T12:40:16.46465+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 13 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T12:40:21.41026+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.792697ms 2023-05-18T12:40:21.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:21.41039+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.897411ms 2023-05-18T12:40:21.41044+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:26.40993+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.950599ms 2023-05-18T12:40:26.41023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:26.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.322116ms 2023-05-18T12:40:26.41073+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:31.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.180702ms 2023-05-18T12:40:31.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:31.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.137214ms 2023-05-18T12:40:31.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:36.40339+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.169127ms 2023-05-18T12:40:36.40347+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:36.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.412305ms 2023-05-18T12:40:36.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:41.40728+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.611169ms 2023-05-18T12:40:41.40735+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:41.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.079301ms 2023-05-18T12:40:41.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:46.41556+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.104614ms 2023-05-18T12:40:46.41564+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:46.42367+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.933699ms 2023-05-18T12:40:46.42372+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:46.46144+08:00 ERROR [539043,b2e01dccea8ae3e6] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:40:51.4112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.324304ms 2023-05-18T12:40:51.41126+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:51.41134+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.483918ms 2023-05-18T12:40:51.41137+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:56.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.075201ms 2023-05-18T12:40:56.41054+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:40:56.41062+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.239215ms 2023-05-18T12:40:56.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:01.40266+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.83461ms 2023-05-18T12:41:01.40272+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:01.40921+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.76811ms 2023-05-18T12:41:01.40926+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:06.4119+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.046213ms 2023-05-18T12:41:06.41197+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:06.41207+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.184927ms 2023-05-18T12:41:06.41211+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:11.41155+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.521306ms 2023-05-18T12:41:11.41162+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:11.41172+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.738522ms 2023-05-18T12:41:11.41175+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:16.40209+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.974412ms 2023-05-18T12:41:16.40216+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:16.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.362204ms 2023-05-18T12:41:16.41066+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:16.41135+08:00 ERROR [539043,4a603c9d97a1e462] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:41:21.40867+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.653582ms 2023-05-18T12:41:21.40874+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:21.41385+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.60592ms 2023-05-18T12:41:21.4139+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:26.41036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.256203ms 2023-05-18T12:41:26.41044+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:26.41051+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.222215ms 2023-05-18T12:41:26.41054+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:31.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.981499ms 2023-05-18T12:41:31.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:31.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.217315ms 2023-05-18T12:41:31.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:36.41133+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.515406ms 2023-05-18T12:41:36.41141+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:36.41148+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.511418ms 2023-05-18T12:41:36.41152+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:41.40324+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.413117ms 2023-05-18T12:41:41.40333+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:41.40862+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.098401ms 2023-05-18T12:41:41.40867+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:46.42049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.091301ms 2023-05-18T12:41:46.42055+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:46.42064+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.646132ms 2023-05-18T12:41:46.42068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:46.44606+08:00 ERROR [539043,567596135b88f171] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:41:51.40245+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.015913ms 2023-05-18T12:41:51.40252+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:51.40818+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.0287ms 2023-05-18T12:41:51.40822+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:56.4048+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.038637ms 2023-05-18T12:41:56.40488+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:41:56.41061+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.105401ms 2023-05-18T12:41:56.41066+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:01.40997+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.0211ms 2023-05-18T12:42:01.41004+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:01.41012+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.951411ms 2023-05-18T12:42:01.41015+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:06.40243+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.971011ms 2023-05-18T12:42:06.4025+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:06.41092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.393304ms 2023-05-18T12:42:06.41099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:11.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.050413ms 2023-05-18T12:42:11.41053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:11.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.309803ms 2023-05-18T12:42:11.41063+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:16.40175+08:00 ERROR [539043,9f7a7560444eb3b8] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:42:16.40187+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.679108ms 2023-05-18T12:42:16.40191+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:16.40795+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.071801ms 2023-05-18T12:42:16.40799+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:21.40857+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.631983ms 2023-05-18T12:42:21.40865+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:21.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.991599ms 2023-05-18T12:42:21.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:26.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.948099ms 2023-05-18T12:42:26.41041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:26.41048+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.968712ms 2023-05-18T12:42:26.41052+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:31.41029+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.920799ms 2023-05-18T12:42:31.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:31.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.003212ms 2023-05-18T12:42:31.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:36.40509+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.756046ms 2023-05-18T12:42:36.40515+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:36.41144+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.167715ms 2023-05-18T12:42:36.41148+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:41.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.149101ms 2023-05-18T12:42:41.41068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:41.41075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.083813ms 2023-05-18T12:42:41.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:46.42538+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.252428ms 2023-05-18T12:42:46.42545+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:46.42571+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=26.775634ms 2023-05-18T12:42:46.42575+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:46.46628+08:00 ERROR [539043,e1d3437cc9a4b6c8] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:42:51.40274+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.034413ms 2023-05-18T12:42:51.4028+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:51.40857+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.156802ms 2023-05-18T12:42:51.40864+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:56.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.176902ms 2023-05-18T12:42:56.41087+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:42:56.41094+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.60562ms 2023-05-18T12:42:56.41097+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:01.41129+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.331716ms 2023-05-18T12:43:01.41137+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:01.41257+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.770709ms 2023-05-18T12:43:01.41264+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:06.40312+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.119314ms 2023-05-18T12:43:06.40319+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:06.41139+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.156502ms 2023-05-18T12:43:06.41143+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:11.41117+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.70462ms 2023-05-18T12:43:11.41123+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:11.41129+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.456305ms 2023-05-18T12:43:11.41134+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:16.4034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.673021ms 2023-05-18T12:43:16.40347+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:16.41905+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.540294ms 2023-05-18T12:43:16.41911+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:16.41985+08:00 ERROR [539043,1d08cd0efd4b0b63] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:43:21.4112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.0252ms 2023-05-18T12:43:21.41126+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:21.41134+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.389917ms 2023-05-18T12:43:21.41138+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:26.40843+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=14.614182ms 2023-05-18T12:43:26.40851+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:26.41419+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.904948ms 2023-05-18T12:43:26.41436+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:31.41337+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.875848ms 2023-05-18T12:43:31.41344+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:31.41949+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.028137ms 2023-05-18T12:43:31.41954+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:36.41166+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.399905ms 2023-05-18T12:43:36.41174+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:36.41184+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.968024ms 2023-05-18T12:43:36.41187+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:41.41213+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.943411ms 2023-05-18T12:43:41.4122+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:41.41229+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.637232ms 2023-05-18T12:43:41.41232+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:46.43382+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=26.903735ms 2023-05-18T12:43:46.43391+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:46.43404+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=27.660745ms 2023-05-18T12:43:46.43407+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:46.45516+08:00 ERROR [539043,d88120bba20988de] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:43:51.41329+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.757146ms 2023-05-18T12:43:51.41336+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:51.41574+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.069563ms 2023-05-18T12:43:51.4158+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:56.40201+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.81841ms 2023-05-18T12:43:56.40208+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:43:56.40793+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.093901ms 2023-05-18T12:43:56.408+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:01.41107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.958911ms 2023-05-18T12:44:01.41114+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:01.41125+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.748222ms 2023-05-18T12:44:01.41128+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:06.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.919399ms 2023-05-18T12:44:06.41052+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:06.41061+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.984312ms 2023-05-18T12:44:06.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:11.40897+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.323791ms 2023-05-18T12:44:11.40905+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:11.41028+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.971499ms 2023-05-18T12:44:11.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:16.40245+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.973512ms 2023-05-18T12:44:16.40251+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:16.41062+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.0333ms 2023-05-18T12:44:16.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:16.41131+08:00 ERROR [539043,03022892ba22efbe] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:44:21.41005+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.81971ms 2023-05-18T12:44:21.41011+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:21.41016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.245502ms 2023-05-18T12:44:21.4102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:26.40176+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.79541ms 2023-05-18T12:44:26.40184+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:26.40888+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.272003ms 2023-05-18T12:44:26.40893+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:31.40502+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.368342ms 2023-05-18T12:44:31.40508+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:31.41421+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.082413ms 2023-05-18T12:44:31.41426+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:36.40311+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.099325ms 2023-05-18T12:44:36.40317+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:36.41024+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.315603ms 2023-05-18T12:44:36.4103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:41.41066+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.173602ms 2023-05-18T12:44:41.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:41.41082+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.171614ms 2023-05-18T12:44:41.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:46.43046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=31.523193ms 2023-05-18T12:44:46.43053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:46.43059+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=22.759584ms 2023-05-18T12:44:46.43063+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:46.45443+08:00 ERROR [539043,3d195cc74c348bbd] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:44:51.40513+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.131239ms 2023-05-18T12:44:51.4052+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:51.41084+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.085001ms 2023-05-18T12:44:51.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:56.41026+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.119201ms 2023-05-18T12:44:56.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:44:56.41039+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.199814ms 2023-05-18T12:44:56.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:01.41008+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.131601ms 2023-05-18T12:45:01.41014+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:01.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.80291ms 2023-05-18T12:45:01.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:06.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.421505ms 2023-05-18T12:45:06.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:06.41092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.500518ms 2023-05-18T12:45:06.41095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:11.41026+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.242703ms 2023-05-18T12:45:11.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:11.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.238314ms 2023-05-18T12:45:11.41043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:16.40285+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.032613ms 2023-05-18T12:45:16.40291+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:16.4109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.956199ms 2023-05-18T12:45:16.41095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:16.4116+08:00 ERROR [539043,027dd5a6204ff8ad] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:45:21.41097+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.359104ms 2023-05-18T12:45:21.41103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:21.41111+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.379317ms 2023-05-18T12:45:21.41115+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:26.40742+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.66967ms 2023-05-18T12:45:26.40749+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:26.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.171902ms 2023-05-18T12:45:26.41082+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:31.41054+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.063001ms 2023-05-18T12:45:31.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:31.41088+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.156914ms 2023-05-18T12:45:31.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:36.40281+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.82961ms 2023-05-18T12:45:36.40287+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:36.41092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.0072ms 2023-05-18T12:45:36.41097+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:41.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.733109ms 2023-05-18T12:45:41.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:41.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.351405ms 2023-05-18T12:45:41.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:46.42481+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.742433ms 2023-05-18T12:45:46.42488+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:46.42496+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=27.163238ms 2023-05-18T12:45:46.42499+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:46.46457+08:00 ERROR [539043,68609393d821bd47] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:45:46.47836+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 1198940 fields:, error="open /proc/1198940/status: no such file or directory" 2023-05-18T12:45:46.47841+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 1198961 fields: error="open /proc/1198961/status: no such file or directory" 2023-05-18T12:45:51.41047+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.093001ms 2023-05-18T12:45:51.41053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:51.41062+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.152414ms 2023-05-18T12:45:51.41065+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:56.40264+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.644208ms 2023-05-18T12:45:56.4027+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:45:56.40869+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.054ms 2023-05-18T12:45:56.40874+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:01.40568+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.545656ms 2023-05-18T12:46:01.40574+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:01.4099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.0125ms 2023-05-18T12:46:01.40995+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:06.4107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.068001ms 2023-05-18T12:46:06.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:06.41087+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.063213ms 2023-05-18T12:46:06.4109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:11.41062+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.189002ms 2023-05-18T12:46:11.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:11.41076+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.909311ms 2023-05-18T12:46:11.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:16.40242+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.213115ms 2023-05-18T12:46:16.40248+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:16.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.780097ms 2023-05-18T12:46:16.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:16.411+08:00 ERROR [539043,dfdc216b2346d1bd] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:46:21.40182+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.84021ms 2023-05-18T12:46:21.40188+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:21.40797+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.389605ms 2023-05-18T12:46:21.40802+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:26.41243+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.179402ms 2023-05-18T12:46:26.4125+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:26.41258+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.637333ms 2023-05-18T12:46:26.41262+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:31.41152+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.905599ms 2023-05-18T12:46:31.41162+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:31.41173+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.254927ms 2023-05-18T12:46:31.41176+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:36.41089+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.210102ms 2023-05-18T12:46:36.41098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:36.41107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.948023ms 2023-05-18T12:46:36.41111+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:41.41128+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.739509ms 2023-05-18T12:46:41.41135+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:41.41142+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.198827ms 2023-05-18T12:46:41.41145+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:46.43068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=25.574718ms 2023-05-18T12:46:46.43074+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:46.43079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=26.139526ms 2023-05-18T12:46:46.43081+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:46.4472+08:00 ERROR [539043,e34c4fe16c02a0b7] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:46:51.41028+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.392504ms 2023-05-18T12:46:51.41034+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:51.41083+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.0462ms 2023-05-18T12:46:51.41088+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:56.41054+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.931099ms 2023-05-18T12:46:56.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:46:56.41263+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.971836ms 2023-05-18T12:46:56.41267+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:01.4053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.564644ms 2023-05-18T12:47:01.40536+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:01.41344+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.0412ms 2023-05-18T12:47:01.41348+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:06.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.140801ms 2023-05-18T12:47:06.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:06.41087+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.709121ms 2023-05-18T12:47:06.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:11.41319+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.179839ms 2023-05-18T12:47:11.41326+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:11.42651+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.068788ms 2023-05-18T12:47:11.42657+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:16.40242+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.749609ms 2023-05-18T12:47:16.40248+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:16.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.054701ms 2023-05-18T12:47:16.41063+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:16.41131+08:00 ERROR [539043,aa4f35ee4851dfac] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:47:21.40593+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.184252ms 2023-05-18T12:47:21.406+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:21.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.0229ms 2023-05-18T12:47:21.41074+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:26.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.900395ms 2023-05-18T12:47:26.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:26.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.279007ms 2023-05-18T12:47:26.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:31.40988+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.051797ms 2023-05-18T12:47:31.40994+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:31.41003+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.849803ms 2023-05-18T12:47:31.41006+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:36.40443+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.220135ms 2023-05-18T12:47:36.4045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:36.40993+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.750494ms 2023-05-18T12:47:36.40997+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:41.40976+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.767794ms 2023-05-18T12:47:41.40982+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:41.40988+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.811602ms 2023-05-18T12:47:41.40993+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:46.42339+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.311784ms 2023-05-18T12:47:46.42346+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:46.42351+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.952292ms 2023-05-18T12:47:46.42354+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:46.44062+08:00 ERROR [539043,204434fa089fcd8d] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:47:51.41023+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.995297ms 2023-05-18T12:47:51.4103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:51.41038+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.236707ms 2023-05-18T12:47:51.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:56.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.176998ms 2023-05-18T12:47:56.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:47:56.41065+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.027505ms 2023-05-18T12:47:56.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:01.41071+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.031097ms 2023-05-18T12:48:01.41077+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:01.41085+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.159106ms 2023-05-18T12:48:01.41088+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:06.40755+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.542163ms 2023-05-18T12:48:06.40764+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:06.411+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.219999ms 2023-05-18T12:48:06.41105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:11.40955+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.813594ms 2023-05-18T12:48:11.40962+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:11.40972+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.5994ms 2023-05-18T12:48:11.40975+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:16.40295+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.454314ms 2023-05-18T12:48:16.40302+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:16.41099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.923895ms 2023-05-18T12:48:16.41103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:16.41172+08:00 ERROR [539043,fb4febb18eeee81e] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:48:21.4079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=14.179371ms 2023-05-18T12:48:21.40797+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:21.41059+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.889695ms 2023-05-18T12:48:21.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:26.40601+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.61494ms 2023-05-18T12:48:26.40607+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:26.4142+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.076397ms 2023-05-18T12:48:26.41424+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:31.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.729093ms 2023-05-18T12:48:31.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:31.41122+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.504211ms 2023-05-18T12:48:31.41126+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:36.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.062197ms 2023-05-18T12:48:36.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:36.41061+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.050105ms 2023-05-18T12:48:36.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:41.40801+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.348272ms 2023-05-18T12:48:41.40809+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:41.41029+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.876595ms 2023-05-18T12:48:41.41034+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:46.40795+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.935808ms 2023-05-18T12:48:46.408+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:46.41628+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.244799ms 2023-05-18T12:48:46.41634+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:46.45535+08:00 ERROR [539043,fdd870b4b658b337] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:48:51.40371+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.724029ms 2023-05-18T12:48:51.40378+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:51.41222+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.526214ms 2023-05-18T12:48:51.41227+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:56.41059+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.197299ms 2023-05-18T12:48:56.41065+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:48:56.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.248007ms 2023-05-18T12:48:56.41076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:01.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.162598ms 2023-05-18T12:49:01.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:01.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.039205ms 2023-05-18T12:49:01.41036+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:06.41125+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.220999ms 2023-05-18T12:49:06.41133+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:06.41142+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.549811ms 2023-05-18T12:49:06.41146+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:11.41005+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.583792ms 2023-05-18T12:49:11.41012+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:11.41019+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.344196ms 2023-05-18T12:49:11.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:16.40272+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.004609ms 2023-05-18T12:49:16.40278+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:16.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.611492ms 2023-05-18T12:49:16.41048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:16.4116+08:00 ERROR [539043,fb29defdd2a295ee] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:49:21.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.2609ms 2023-05-18T12:49:21.41041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:21.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.073405ms 2023-05-18T12:49:21.41053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:26.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.795694ms 2023-05-18T12:49:26.41023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:26.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.524699ms 2023-05-18T12:49:26.41036+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:31.41078+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.184098ms 2023-05-18T12:49:31.41086+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:31.41128+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.511711ms 2023-05-18T12:49:31.41132+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:36.40397+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.188522ms 2023-05-18T12:49:36.40404+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:36.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.053597ms 2023-05-18T12:49:36.4104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:41.41005+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.185399ms 2023-05-18T12:49:41.41011+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:41.41016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.158806ms 2023-05-18T12:49:41.41019+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:46.42419+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.684701ms 2023-05-18T12:49:46.42426+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:46.42432+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.293697ms 2023-05-18T12:49:46.42435+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:46.43799+08:00 ERROR [539043,e4a87924fa912a21] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:49:51.40176+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.790906ms 2023-05-18T12:49:51.40183+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:51.409+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.396301ms 2023-05-18T12:49:51.40905+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:56.41062+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.706593ms 2023-05-18T12:49:56.41068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:49:56.41075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.858202ms 2023-05-18T12:49:56.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:01.40397+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.318024ms 2023-05-18T12:50:01.40404+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:01.4107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.102498ms 2023-05-18T12:50:01.41074+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:06.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.174398ms 2023-05-18T12:50:06.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:06.41094+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.248208ms 2023-05-18T12:50:06.41097+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:11.41065+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.920796ms 2023-05-18T12:50:11.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:11.41078+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.036605ms 2023-05-18T12:50:11.41081+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:16.40208+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.748206ms 2023-05-18T12:50:16.40215+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:16.40977+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.584691ms 2023-05-18T12:50:16.40982+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:16.41055+08:00 ERROR [539043,85a42a061ab4ea81] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:50:16.46478+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields:, module=monitor.ob, duration="20.5µs" 2023-05-18T12:50:16.46484+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields:, module=monitor.ob, eventType=add, duration="5.5µs" 2023-05-18T12:50:16.46486+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields: module=monitor.ob, duration="4µs" 2023-05-18T12:50:16.4649+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields:, module=monitor.ob, eventType=add, duration="3.9µs" 2023-05-18T12:50:16.46493+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T12:50:16.47244+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc0004f8820 0xc0004f88c0 0xc0004f8960 0xc0004f8a00 0xc0004f8aa0 0xc0004f8b40 0xc0004f8be0 0xc0004f8c80 0xc0004f8d20 0xc0004f8dc0 0xc0004f8e60 0xc0004f8f00 0xc0004f8fa0 0xc0004f9040 0xc0004f90e0 0xc0004f9180 0xc0004f9220 0xc0004f92c0 0xc0004f9360 0xc0004f9400 0xc0004f94a0 0xc0004f9540 0xc0004f95e0 0xc0004f9680 0xc0004f9720 0xc0004f97c0 0xc0004f9860 0xc0004f9900 0xc0004f99a0 0xc0004f9a40 0xc0004f9ae0] CollectInterval:1s TimeAlign:false} 2023-05-18T12:50:16.47446+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T12:50:16.47449+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields:, input=mysqlTableInput, duration="4.7µs" 2023-05-18T12:50:16.47451+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields: input=mysqlTableInput, duration="25.8µs" 2023-05-18T12:50:16.47454+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields: eventType=add, error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)", duration=9.640116ms, module=monitor.ob 2023-05-18T12:50:16.47456+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields: module=monitor.ob, eventType=add, duration=9.659316ms 2023-05-18T12:50:16.47459+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields: duration=9.731117ms, module=monitor.ob 2023-05-18T12:50:16.47461+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields: eventType=add, duration=9.776618ms, module=monitor.ob 2023-05-18T12:50:16.47463+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields:, module=monitor.ob, duration=9.866519ms 2023-05-18T12:50:16.47468+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 14 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T12:50:21.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.676492ms 2023-05-18T12:50:21.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:21.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.722601ms 2023-05-18T12:50:21.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:26.40994+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.885695ms 2023-05-18T12:50:26.41001+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:26.41007+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.695801ms 2023-05-18T12:50:26.4101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:31.40452+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.762629ms 2023-05-18T12:50:31.4046+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:31.41009+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.701892ms 2023-05-18T12:50:31.41014+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:36.41118+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.725905ms 2023-05-18T12:50:36.41125+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:36.41132+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.291021ms 2023-05-18T12:50:36.41135+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:41.40966+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.703793ms 2023-05-18T12:50:41.40973+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:41.40982+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.629001ms 2023-05-18T12:50:41.40985+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:46.41662+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.214411ms 2023-05-18T12:50:46.41668+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:46.42486+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.081798ms 2023-05-18T12:50:46.42491+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:46.45161+08:00 ERROR [539043,75e2a2a49ccab6fb] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:50:51.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.190998ms 2023-05-18T12:50:51.41092+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:51.411+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.358509ms 2023-05-18T12:50:51.41103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:56.41087+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.3248ms 2023-05-18T12:50:56.41094+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:50:56.41102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.352308ms 2023-05-18T12:50:56.41105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:01.40348+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.375225ms 2023-05-18T12:51:01.40356+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:01.41268+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.015321ms 2023-05-18T12:51:01.41275+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:06.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.387801ms 2023-05-18T12:51:06.41027+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:06.41037+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.195707ms 2023-05-18T12:51:06.4104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:11.41047+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.935895ms 2023-05-18T12:51:11.41055+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:11.41064+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.099306ms 2023-05-18T12:51:11.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:16.40505+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.491338ms 2023-05-18T12:51:16.40512+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:16.41463+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.468214ms 2023-05-18T12:51:16.41469+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:16.41549+08:00 ERROR [539043,77ae23ebfc3bda05] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:51:21.41065+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.302ms 2023-05-18T12:51:21.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:21.41081+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.150507ms 2023-05-18T12:51:21.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:26.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.004897ms 2023-05-18T12:51:26.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:26.41087+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.901404ms 2023-05-18T12:51:26.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:31.4123+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.438002ms 2023-05-18T12:51:31.41237+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:31.41247+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.017129ms 2023-05-18T12:51:31.4125+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:36.40623+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.866955ms 2023-05-18T12:51:36.40629+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:36.41023+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.065997ms 2023-05-18T12:51:36.41028+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:41.40657+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.849054ms 2023-05-18T12:51:41.40665+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:41.41036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.814394ms 2023-05-18T12:51:41.41041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:46.41286+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.83499ms 2023-05-18T12:51:46.41294+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:46.43905+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.682721ms 2023-05-18T12:51:46.43911+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:46.46047+08:00 ERROR [539043,d3c65dafc194b882] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:51:51.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.839295ms 2023-05-18T12:51:51.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:51.41047+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.850002ms 2023-05-18T12:51:51.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:56.41128+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.697604ms 2023-05-18T12:51:56.41135+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:51:56.41193+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.120818ms 2023-05-18T12:51:56.41198+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:01.41078+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.256899ms 2023-05-18T12:52:01.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:01.41096+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.108006ms 2023-05-18T12:52:01.41101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:06.40999+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.115498ms 2023-05-18T12:52:06.41006+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:06.41013+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.987105ms 2023-05-18T12:52:06.41016+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:11.40179+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.325301ms 2023-05-18T12:52:11.40185+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:11.40806+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.006196ms 2023-05-18T12:52:11.40812+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:16.40243+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.685604ms 2023-05-18T12:52:16.40249+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:16.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.787294ms 2023-05-18T12:52:16.41036+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:16.41103+08:00 ERROR [539043,ed3dede298e19bdc] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:52:21.41104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.055097ms 2023-05-18T12:52:21.41112+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:21.4112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.215407ms 2023-05-18T12:52:21.41123+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:26.40979+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.854894ms 2023-05-18T12:52:26.40986+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:26.40995+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.5982ms 2023-05-18T12:52:26.40998+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:31.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.966896ms 2023-05-18T12:52:31.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:31.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.41181ms 2023-05-18T12:52:31.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:36.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.986496ms 2023-05-18T12:52:36.41028+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:36.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.839002ms 2023-05-18T12:52:36.41041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:41.41029+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.2758ms 2023-05-18T12:52:41.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:41.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.064605ms 2023-05-18T12:52:41.41045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:46.41825+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.002393ms 2023-05-18T12:52:46.41831+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:46.41837+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.678689ms 2023-05-18T12:52:46.4184+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:46.45324+08:00 ERROR [539043,f0c4aa2f4048cb75] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:52:51.41054+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.561399ms 2023-05-18T12:52:51.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:51.41071+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.207999ms 2023-05-18T12:52:51.41074+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:56.41099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.512202ms 2023-05-18T12:52:56.41106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:52:56.41114+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.405909ms 2023-05-18T12:52:56.41118+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:01.4063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.755253ms 2023-05-18T12:53:01.40637+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:01.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.080798ms 2023-05-18T12:53:01.41036+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:06.41111+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.731205ms 2023-05-18T12:53:06.41119+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:06.41127+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.529711ms 2023-05-18T12:53:06.41131+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:11.40217+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.739605ms 2023-05-18T12:53:11.40224+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:11.40805+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.977096ms 2023-05-18T12:53:11.4081+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:16.40238+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.202911ms 2023-05-18T12:53:16.40246+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:16.41064+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.144598ms 2023-05-18T12:53:16.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:16.41136+08:00 ERROR [539043,dd85ffdf91d6fe54] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:53:21.41095+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.061397ms 2023-05-18T12:53:21.41102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:21.41109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.104305ms 2023-05-18T12:53:21.41113+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:26.40562+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.608052ms 2023-05-18T12:53:26.4057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:26.40999+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.185598ms 2023-05-18T12:53:26.41004+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:31.40998+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.965795ms 2023-05-18T12:53:31.41007+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:31.41015+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.731901ms 2023-05-18T12:53:31.41018+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:36.41331+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.614536ms 2023-05-18T12:53:36.41341+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:36.41434+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.086145ms 2023-05-18T12:53:36.41439+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:41.40987+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.716201ms 2023-05-18T12:53:41.41009+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:41.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.385901ms 2023-05-18T12:53:41.41063+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:46.41614+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.814806ms 2023-05-18T12:53:46.41621+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:46.42431+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.980996ms 2023-05-18T12:53:46.42436+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:46.45674+08:00 ERROR [539043,71ffd9836f2c51b8] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:53:46.48182+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 1253736 fields:, error="open /proc/1253736/status: no such file or directory" 2023-05-18T12:53:51.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.372401ms 2023-05-18T12:53:51.4104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:51.41047+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.177707ms 2023-05-18T12:53:51.41053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:56.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.242699ms 2023-05-18T12:53:56.41097+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:53:56.41105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.43551ms 2023-05-18T12:53:56.41108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:01.4098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.562591ms 2023-05-18T12:54:01.40987+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:01.40995+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.6401ms 2023-05-18T12:54:01.40998+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:06.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.175199ms 2023-05-18T12:54:06.41059+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:06.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.948104ms 2023-05-18T12:54:06.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:11.40694+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.002857ms 2023-05-18T12:54:11.407+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:11.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.915495ms 2023-05-18T12:54:11.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:16.40238+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.987008ms 2023-05-18T12:54:16.40244+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:16.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.657392ms 2023-05-18T12:54:16.41025+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:16.41093+08:00 ERROR [539043,1fe6cbdca8f6be4e] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:54:21.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.918403ms 2023-05-18T12:54:21.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:21.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.350801ms 2023-05-18T12:54:21.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:26.41137+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.198999ms 2023-05-18T12:54:26.41144+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:26.41152+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.683612ms 2023-05-18T12:54:26.41155+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:31.40311+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.115321ms 2023-05-18T12:54:31.40318+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:31.41008+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.272799ms 2023-05-18T12:54:31.41013+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:36.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.126898ms 2023-05-18T12:54:36.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:36.41075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.996405ms 2023-05-18T12:54:36.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:41.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.109998ms 2023-05-18T12:54:41.41075+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:41.41085+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.217507ms 2023-05-18T12:54:41.41088+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:46.4323+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=25.416706ms 2023-05-18T12:54:46.43237+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:46.43242+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.067014ms 2023-05-18T12:54:46.43245+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:46.45459+08:00 ERROR [539043,d31e90fabc0a9ab1] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:54:51.41078+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.3347ms 2023-05-18T12:54:51.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:51.41094+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.729513ms 2023-05-18T12:54:51.41097+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:56.4098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.663093ms 2023-05-18T12:54:56.40987+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:54:56.40996+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.700101ms 2023-05-18T12:54:56.40999+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:01.41117+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.3487ms 2023-05-18T12:55:01.41123+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:01.41131+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.340109ms 2023-05-18T12:55:01.41134+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:06.41081+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.351ms 2023-05-18T12:55:06.41088+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:06.41097+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.233107ms 2023-05-18T12:55:06.411+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:11.40178+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.815207ms 2023-05-18T12:55:11.40185+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:11.40779+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.204599ms 2023-05-18T12:55:11.40784+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:16.40248+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.929407ms 2023-05-18T12:55:16.40254+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:16.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.905096ms 2023-05-18T12:55:16.41055+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:16.41123+08:00 ERROR [539043,47cfc13d6598f805] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:55:21.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.233199ms 2023-05-18T12:55:21.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:21.41047+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.069905ms 2023-05-18T12:55:21.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:26.40175+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.795106ms 2023-05-18T12:55:26.40182+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:26.40947+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.857107ms 2023-05-18T12:55:26.40953+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:31.41001+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.751293ms 2023-05-18T12:55:31.41008+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:31.41016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.425498ms 2023-05-18T12:55:31.41019+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:36.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.294199ms 2023-05-18T12:55:36.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:36.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.928603ms 2023-05-18T12:55:36.41045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:41.40634+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.44755ms 2023-05-18T12:55:41.40641+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:41.41059+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.119897ms 2023-05-18T12:55:41.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:46.42453+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.675212ms 2023-05-18T12:55:46.42461+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:46.42467+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.27692ms 2023-05-18T12:55:46.42471+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:46.43719+08:00 ERROR [539043,8e1af18778d0c285] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:55:51.41095+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.386101ms 2023-05-18T12:55:51.41102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:51.4111+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.46541ms 2023-05-18T12:55:51.41113+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:56.41038+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.981396ms 2023-05-18T12:55:56.41045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:55:56.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.952104ms 2023-05-18T12:55:56.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:01.41038+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.813094ms 2023-05-18T12:56:01.41045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:01.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.6626ms 2023-05-18T12:56:01.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:06.40228+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.687204ms 2023-05-18T12:56:06.40237+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:06.40826+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.050197ms 2023-05-18T12:56:06.40831+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:11.40524+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.61644ms 2023-05-18T12:56:11.4053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:11.41113+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.2665ms 2023-05-18T12:56:11.41118+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:16.40267+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.999808ms 2023-05-18T12:56:16.40276+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:16.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.50159ms 2023-05-18T12:56:16.41036+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:16.41103+08:00 ERROR [539043,46119e36d5c81886] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:56:21.41182+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.236699ms 2023-05-18T12:56:21.4119+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:21.41199+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.080517ms 2023-05-18T12:56:21.41203+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:26.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.172598ms 2023-05-18T12:56:26.41075+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:26.41083+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.988605ms 2023-05-18T12:56:26.41087+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:31.41011+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.092797ms 2023-05-18T12:56:31.41017+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:31.41025+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.984805ms 2023-05-18T12:56:31.41028+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:36.40619+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.600152ms 2023-05-18T12:56:36.40626+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:36.42224+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.229207ms 2023-05-18T12:56:36.42232+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:41.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.223099ms 2023-05-18T12:56:41.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:41.41085+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.609412ms 2023-05-18T12:56:41.41088+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:46.41601+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.880907ms 2023-05-18T12:56:46.41608+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:46.42464+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.469702ms 2023-05-18T12:56:46.4247+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:46.46877+08:00 ERROR [539043,bb761fdd22ebbab3] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:56:51.41097+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.560903ms 2023-05-18T12:56:51.41111+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:51.41119+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.000617ms 2023-05-18T12:56:51.41125+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:56.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.123798ms 2023-05-18T12:56:56.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:56:56.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.883103ms 2023-05-18T12:56:56.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:01.41013+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.141698ms 2023-05-18T12:57:01.4102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:01.41029+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.966504ms 2023-05-18T12:57:01.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:06.40316+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.292611ms 2023-05-18T12:57:06.40324+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:06.40899+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.466502ms 2023-05-18T12:57:06.40905+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:11.41028+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.194198ms 2023-05-18T12:57:11.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:11.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.189707ms 2023-05-18T12:57:11.41045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:16.40261+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.16761ms 2023-05-18T12:57:16.40267+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:16.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.080098ms 2023-05-18T12:57:16.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:16.41153+08:00 ERROR [539043,ddd4f66f315ee950] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:57:21.41066+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.3112ms 2023-05-18T12:57:21.41075+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:21.41087+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.232708ms 2023-05-18T12:57:21.4109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:26.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.181998ms 2023-05-18T12:57:26.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:26.41089+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.181707ms 2023-05-18T12:57:26.41094+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:31.40165+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.680204ms 2023-05-18T12:57:31.40172+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:31.40751+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.940795ms 2023-05-18T12:57:31.40755+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:36.41001+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.948196ms 2023-05-18T12:57:36.41008+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:36.41015+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.916403ms 2023-05-18T12:57:36.41019+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:41.41041+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.110098ms 2023-05-18T12:57:41.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:41.41054+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.906003ms 2023-05-18T12:57:41.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:46.40629+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.975208ms 2023-05-18T12:57:46.40635+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:46.4142+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.818994ms 2023-05-18T12:57:46.41425+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:46.44956+08:00 ERROR [539043,65ab1cdd63013c5b] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:57:51.404+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.693029ms 2023-05-18T12:57:51.40406+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:51.41059+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.270099ms 2023-05-18T12:57:51.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:56.40237+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.561603ms 2023-05-18T12:57:56.40243+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:57:56.40796+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.836695ms 2023-05-18T12:57:56.40802+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:01.40338+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.384925ms 2023-05-18T12:58:01.40345+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:01.40969+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.843795ms 2023-05-18T12:58:01.40975+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:06.40997+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.770393ms 2023-05-18T12:58:06.41003+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:06.4101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.6223ms 2023-05-18T12:58:06.41012+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:11.41061+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.195899ms 2023-05-18T12:58:11.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:11.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.973404ms 2023-05-18T12:58:11.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:16.40168+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.685205ms 2023-05-18T12:58:16.40175+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:16.40959+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.760494ms 2023-05-18T12:58:16.40964+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:16.41029+08:00 ERROR [539043,da3d2e031633e0c7] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:58:21.40603+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.181647ms 2023-05-18T12:58:21.4061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:21.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.024897ms 2023-05-18T12:58:21.41063+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:26.40955+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.591892ms 2023-05-18T12:58:26.40962+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:26.40969+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.560999ms 2023-05-18T12:58:26.40972+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:31.40216+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.171511ms 2023-05-18T12:58:31.40222+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:31.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.129898ms 2023-05-18T12:58:31.41048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:36.41023+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.948704ms 2023-05-18T12:58:36.4103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:36.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.256799ms 2023-05-18T12:58:36.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:41.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.990596ms 2023-05-18T12:58:41.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:41.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.38761ms 2023-05-18T12:58:41.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:46.42267+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.78279ms 2023-05-18T12:58:46.42273+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:46.42293+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.547599ms 2023-05-18T12:58:46.42297+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:46.44247+08:00 ERROR [539043,0fe35f8f61fc95d2] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:58:51.40188+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.577703ms 2023-05-18T12:58:51.40194+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:51.40791+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.043096ms 2023-05-18T12:58:51.40796+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:56.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.107097ms 2023-05-18T12:58:56.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:58:56.41076+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.055005ms 2023-05-18T12:58:56.41081+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:01.40978+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.536799ms 2023-05-18T12:59:01.40984+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:01.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.088297ms 2023-05-18T12:59:01.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:06.40164+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.658004ms 2023-05-18T12:59:06.4017+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:06.40811+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.3748ms 2023-05-18T12:59:06.40816+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:11.40197+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.725205ms 2023-05-18T12:59:11.40203+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:11.41016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.098097ms 2023-05-18T12:59:11.4102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:16.40356+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.93102ms 2023-05-18T12:59:16.40364+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:16.4121+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.394501ms 2023-05-18T12:59:16.41215+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:16.41288+08:00 ERROR [539043,d437802055fe66b9] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:59:21.41012+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.491499ms 2023-05-18T12:59:21.41018+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:21.41023+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.943495ms 2023-05-18T12:59:21.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:26.40951+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.739593ms 2023-05-18T12:59:26.40957+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:26.40966+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.503699ms 2023-05-18T12:59:26.40969+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:31.41247+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.381101ms 2023-05-18T12:59:31.41254+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:31.41266+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.666025ms 2023-05-18T12:59:31.41269+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:36.41026+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.001796ms 2023-05-18T12:59:36.41034+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:36.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.982904ms 2023-05-18T12:59:36.41045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:41.4015+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.485902ms 2023-05-18T12:59:41.40157+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:41.40758+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.014396ms 2023-05-18T12:59:41.40763+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:46.4342+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=27.269229ms 2023-05-18T12:59:46.43426+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:46.4344+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=28.022337ms 2023-05-18T12:59:46.43444+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:46.45166+08:00 ERROR [539043,387dfbebafb13b02] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T12:59:46.4729+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 1294720 fields: error="open /proc/1294720/status: no such file or directory" 2023-05-18T12:59:51.40516+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.145434ms 2023-05-18T12:59:51.40523+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:51.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.708193ms 2023-05-18T12:59:51.41053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:56.40931+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.399385ms 2023-05-18T12:59:56.40938+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T12:59:56.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.991696ms 2023-05-18T12:59:56.41052+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:01.41116+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.201599ms 2023-05-18T13:00:01.41122+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:01.41129+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.297908ms 2023-05-18T13:00:01.41133+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:06.41011+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.619692ms 2023-05-18T13:00:06.41017+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:06.41024+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.192995ms 2023-05-18T13:00:06.41027+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:11.41149+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.484914ms 2023-05-18T13:00:11.41155+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:11.41164+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.019417ms 2023-05-18T13:00:11.41169+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:16.40509+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.189135ms 2023-05-18T13:00:16.40516+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:16.41295+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.748994ms 2023-05-18T13:00:16.41299+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:16.41411+08:00 ERROR [539043,7aec95222d0217ec] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:00:16.4749+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields:, module=monitor.ob, duration="23.4µs" 2023-05-18T13:00:16.47498+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields:, module=monitor.ob, eventType=add, duration="10.6µs" 2023-05-18T13:00:16.47502+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields:, module=monitor.ob, duration="4.7µs" 2023-05-18T13:00:16.47506+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields:, module=monitor.ob, eventType=add, duration="4.4µs" 2023-05-18T13:00:16.47514+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T13:00:16.47913+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc0002305a0 0xc000230640 0xc0002306e0 0xc000230780 0xc000230820 0xc0002308c0 0xc000230960 0xc000230a00 0xc000230aa0 0xc000230b40 0xc000230be0 0xc000230c80 0xc000230d20 0xc000230dc0 0xc000230e60 0xc000230f00 0xc000230fa0 0xc000231040 0xc0002310e0 0xc000231180 0xc000231220 0xc0002312c0 0xc000231360 0xc000231400 0xc0002314a0 0xc000231540 0xc0002315e0 0xc000231680 0xc000231720 0xc0002317c0 0xc000231860] CollectInterval:1s TimeAlign:false} 2023-05-18T13:00:16.48002+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T13:00:16.48006+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields:, input=mysqlTableInput, duration="4.6µs" 2023-05-18T13:00:16.48008+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields: input=mysqlTableInput, duration="25µs" 2023-05-18T13:00:16.48012+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields:, module=monitor.ob, eventType=add, error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)", duration=5.066361ms 2023-05-18T13:00:16.48015+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields: eventType=add, duration=5.093361ms, module=monitor.ob 2023-05-18T13:00:16.48017+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields:, module=monitor.ob, duration=5.153962ms 2023-05-18T13:00:16.48018+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields: duration=5.208863ms, module=monitor.ob, eventType=add 2023-05-18T13:00:16.48019+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields:, module=monitor.ob, duration=5.319064ms 2023-05-18T13:00:16.48021+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 15 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T13:00:21.402+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.849106ms 2023-05-18T13:00:21.40206+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:21.40789+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.066297ms 2023-05-18T13:00:21.40794+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:26.40617+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.920943ms 2023-05-18T13:00:26.40624+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:26.41446+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.165698ms 2023-05-18T13:00:26.41451+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:31.41023+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.015796ms 2023-05-18T13:00:31.41031+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:31.41038+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.039205ms 2023-05-18T13:00:31.41041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:36.40241+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.596703ms 2023-05-18T13:00:36.40248+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:36.4086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.175599ms 2023-05-18T13:00:36.40866+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:41.41107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.679505ms 2023-05-18T13:00:41.41115+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:41.41124+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.590012ms 2023-05-18T13:00:41.41127+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:46.4309+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.939624ms 2023-05-18T13:00:46.43096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:46.43106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=27.599732ms 2023-05-18T13:00:46.43109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:46.45171+08:00 ERROR [539043,58fb51fbaa78f29b] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:00:51.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.166698ms 2023-05-18T13:00:51.41065+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:51.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.068806ms 2023-05-18T13:00:51.41076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:56.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.148998ms 2023-05-18T13:00:56.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:00:56.41092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.131906ms 2023-05-18T13:00:56.41095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:01.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.884895ms 2023-05-18T13:01:01.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:01.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.858903ms 2023-05-18T13:01:01.41048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:06.4107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.055397ms 2023-05-18T13:01:06.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:06.41087+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.949804ms 2023-05-18T13:01:06.4109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:11.41076+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.2874ms 2023-05-18T13:01:11.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:11.41093+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.45361ms 2023-05-18T13:01:11.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:16.40302+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.410113ms 2023-05-18T13:01:16.40309+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:16.41116+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.020397ms 2023-05-18T13:01:16.41121+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:16.41189+08:00 ERROR [539043,e91cf4c4cea53952] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:01:21.41107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.152298ms 2023-05-18T13:01:21.41113+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:21.4112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.608812ms 2023-05-18T13:01:21.41125+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:26.41257+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.746605ms 2023-05-18T13:01:26.41265+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:26.41273+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.684125ms 2023-05-18T13:01:26.41276+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:31.41105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.108198ms 2023-05-18T13:01:31.41113+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:31.41121+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.195507ms 2023-05-18T13:01:31.41124+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:36.4097+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.594592ms 2023-05-18T13:01:36.40977+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:36.40986+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.419098ms 2023-05-18T13:01:36.40989+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:41.4051+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.59054ms 2023-05-18T13:01:41.40555+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:41.40833+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.613303ms 2023-05-18T13:01:41.40837+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:46.41867+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.734241ms 2023-05-18T13:01:46.41874+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:46.41881+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.360449ms 2023-05-18T13:01:46.41886+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:46.45503+08:00 ERROR [539043,09c284340843cb09] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:01:51.41071+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.856294ms 2023-05-18T13:01:51.41077+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:51.41085+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.829202ms 2023-05-18T13:01:51.41088+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:56.4091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.79499ms 2023-05-18T13:01:56.40918+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:01:56.41066+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.390701ms 2023-05-18T13:01:56.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:01.41011+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.846394ms 2023-05-18T13:02:01.41017+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:01.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.939404ms 2023-05-18T13:02:01.4103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:06.41075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.989396ms 2023-05-18T13:02:06.41081+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:06.41089+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.896403ms 2023-05-18T13:02:06.41093+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:11.40781+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.870367ms 2023-05-18T13:02:11.40787+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:11.41139+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.277099ms 2023-05-18T13:02:11.41144+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:16.40279+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.11201ms 2023-05-18T13:02:16.40285+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:16.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.582791ms 2023-05-18T13:02:16.41054+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:16.41124+08:00 ERROR [539043,1d3519147cf65988] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:02:21.4093+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.47419ms 2023-05-18T13:02:21.40937+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:21.40945+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.119594ms 2023-05-18T13:02:21.40948+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:26.4116+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.395013ms 2023-05-18T13:02:26.41166+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:26.41175+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.26002ms 2023-05-18T13:02:26.41178+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:31.402+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.012409ms 2023-05-18T13:02:31.40206+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:31.40876+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.132498ms 2023-05-18T13:02:31.40881+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:36.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.012196ms 2023-05-18T13:02:36.4104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:36.41047+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.6054ms 2023-05-18T13:02:36.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:41.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.3165ms 2023-05-18T13:02:41.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:41.41065+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.401809ms 2023-05-18T13:02:41.41068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:46.41863+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.419525ms 2023-05-18T13:02:46.4187+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:46.41879+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.072933ms 2023-05-18T13:02:46.41882+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:46.4555+08:00 ERROR [539043,099ea2d528e110f0] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:02:51.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.410502ms 2023-05-18T13:02:51.41073+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:51.41088+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.708713ms 2023-05-18T13:02:51.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:56.41025+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.812294ms 2023-05-18T13:02:56.41033+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:02:56.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.026604ms 2023-05-18T13:02:56.41043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:01.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.941595ms 2023-05-18T13:03:01.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:01.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.006304ms 2023-05-18T13:03:01.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:06.41081+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.341801ms 2023-05-18T13:03:06.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:06.41097+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.735014ms 2023-05-18T13:03:06.41102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:11.41075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.678204ms 2023-05-18T13:03:11.41082+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:11.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.766014ms 2023-05-18T13:03:11.41094+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:16.40307+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.15351ms 2023-05-18T13:03:16.40313+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:16.41136+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.197599ms 2023-05-18T13:03:16.41141+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:16.41204+08:00 ERROR [539043,9828307bc7afc14c] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:03:21.40866+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.00838ms 2023-05-18T13:03:21.40872+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:21.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.385201ms 2023-05-18T13:03:21.41083+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:26.41083+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.207399ms 2023-05-18T13:03:26.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:26.41098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.45481ms 2023-05-18T13:03:26.41103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:31.40812+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.10987ms 2023-05-18T13:03:31.40818+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:31.41126+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.248899ms 2023-05-18T13:03:31.41133+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:36.41112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.3692ms 2023-05-18T13:03:36.41119+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:36.41126+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.391709ms 2023-05-18T13:03:36.41129+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:41.40957+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.49829ms 2023-05-18T13:03:41.40964+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:41.40973+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.359797ms 2023-05-18T13:03:41.40976+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:46.42154+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.251899ms 2023-05-18T13:03:46.42162+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:46.42167+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.494411ms 2023-05-18T13:03:46.4217+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:46.45764+08:00 ERROR [539043,b62a163907724fa7] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:03:51.40991+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.667592ms 2023-05-18T13:03:51.40997+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:51.41006+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.785302ms 2023-05-18T13:03:51.41009+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:56.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.372601ms 2023-05-18T13:03:56.41086+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:03:56.41094+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.299208ms 2023-05-18T13:03:56.41098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:01.4101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.113598ms 2023-05-18T13:04:01.41017+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:01.41028+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.191507ms 2023-05-18T13:04:01.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:06.40211+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.991208ms 2023-05-18T13:04:06.40219+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:06.40827+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.449902ms 2023-05-18T13:04:06.40832+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:11.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.057397ms 2023-05-18T13:04:11.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:11.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.359108ms 2023-05-18T13:04:11.41075+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:16.40231+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.961107ms 2023-05-18T13:04:16.40238+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:16.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.036796ms 2023-05-18T13:04:16.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:16.41116+08:00 ERROR [539043,9fd35d7748a65c18] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:04:21.4082+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.220771ms 2023-05-18T13:04:21.40827+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:21.41164+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.574903ms 2023-05-18T13:04:21.41173+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:26.41015+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.199899ms 2023-05-18T13:04:26.41023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:26.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.088706ms 2023-05-18T13:04:26.41034+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:31.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.692799ms 2023-05-18T13:04:31.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:31.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.943018ms 2023-05-18T13:04:31.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:36.40361+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.279533ms 2023-05-18T13:04:36.40367+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:36.40828+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.242006ms 2023-05-18T13:04:36.40833+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:41.40969+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.717616ms 2023-05-18T13:04:41.40976+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:41.40985+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.017403ms 2023-05-18T13:04:41.40988+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:46.41524+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.265022ms 2023-05-18T13:04:46.4153+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:46.43112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=23.517203ms 2023-05-18T13:04:46.43117+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:46.45049+08:00 ERROR [539043,7b21dab834bfa4b4] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:04:51.41004+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.932418ms 2023-05-18T13:04:51.41011+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:51.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.249306ms 2023-05-18T13:04:51.4102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:56.40989+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.7361ms 2023-05-18T13:04:56.40998+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:04:56.41008+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.353211ms 2023-05-18T13:04:56.41011+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:01.41037+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.027703ms 2023-05-18T13:05:01.41043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:01.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.293923ms 2023-05-18T13:05:01.41055+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:06.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.733099ms 2023-05-18T13:05:06.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:06.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.948918ms 2023-05-18T13:05:06.41081+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:11.40981+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.854201ms 2023-05-18T13:05:11.40989+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:11.40997+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.782217ms 2023-05-18T13:05:11.41+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:16.40295+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.100017ms 2023-05-18T13:05:16.40302+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:16.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.658198ms 2023-05-18T13:05:16.41077+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:16.41152+08:00 ERROR [539043,698238273a60899d] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:05:21.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.586411ms 2023-05-18T13:05:21.41098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:21.41107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.755329ms 2023-05-18T13:05:21.4111+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:26.40865+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.652988ms 2023-05-18T13:05:26.40872+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:26.41102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.179905ms 2023-05-18T13:05:26.41108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:31.41002+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.807101ms 2023-05-18T13:05:31.41009+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:31.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.774116ms 2023-05-18T13:05:31.41021+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:36.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.119505ms 2023-05-18T13:05:36.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:36.41065+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.640114ms 2023-05-18T13:05:36.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:41.41061+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.156905ms 2023-05-18T13:05:41.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:41.41076+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.225422ms 2023-05-18T13:05:41.41081+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:46.41685+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.387521ms 2023-05-18T13:05:46.41691+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:46.42492+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.923702ms 2023-05-18T13:05:46.42497+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:46.44016+08:00 ERROR [539043,a730d18114f7f399] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:05:51.41189+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.662512ms 2023-05-18T13:05:51.41197+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:51.41205+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.355537ms 2023-05-18T13:05:51.41208+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:56.4112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.289207ms 2023-05-18T13:05:56.41127+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:05:56.41142+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.388724ms 2023-05-18T13:05:56.41146+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:01.40248+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.873714ms 2023-05-18T13:06:01.40255+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:01.40836+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.171205ms 2023-05-18T13:06:01.40841+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:06.40963+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.7442ms 2023-05-18T13:06:06.4097+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:06.40978+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.464112ms 2023-05-18T13:06:06.40981+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:11.411+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.7191ms 2023-05-18T13:06:11.41107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:11.41116+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.169722ms 2023-05-18T13:06:11.41119+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:16.40295+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.061617ms 2023-05-18T13:06:16.40303+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:16.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.600498ms 2023-05-18T13:06:16.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:16.41146+08:00 ERROR [539043,a754d656e3afd62c] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:06:21.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.045504ms 2023-05-18T13:06:21.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:21.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.174721ms 2023-05-18T13:06:21.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:26.40989+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.975003ms 2023-05-18T13:06:26.40995+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:26.41002+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.856518ms 2023-05-18T13:06:26.41005+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:31.40265+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.913914ms 2023-05-18T13:06:31.40271+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:31.40872+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.174406ms 2023-05-18T13:06:31.40877+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:36.41061+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.907318ms 2023-05-18T13:06:36.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:36.41075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.080104ms 2023-05-18T13:06:36.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:41.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.531397ms 2023-05-18T13:06:41.4104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:41.41047+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.562313ms 2023-05-18T13:06:41.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:46.43029+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=30.733096ms 2023-05-18T13:06:46.43035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:46.43041+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=31.912411ms 2023-05-18T13:06:46.43043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:46.46563+08:00 ERROR [539043,5f813cc23d19ab57] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:06:51.40315+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.15683ms 2023-05-18T13:06:51.40321+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:51.41048+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.162105ms 2023-05-18T13:06:51.41053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:56.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.239206ms 2023-05-18T13:06:56.41068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:06:56.41075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.335123ms 2023-05-18T13:06:56.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:01.41133+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.123805ms 2023-05-18T13:07:01.4114+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:01.41149+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.83773ms 2023-05-18T13:07:01.41152+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:06.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.943703ms 2023-05-18T13:07:06.41023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:06.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.001319ms 2023-05-18T13:07:06.41033+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:11.41019+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.030404ms 2023-05-18T13:07:11.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:11.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.214022ms 2023-05-18T13:07:11.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:16.40325+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.219519ms 2023-05-18T13:07:16.40331+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:16.41199+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.648112ms 2023-05-18T13:07:16.41204+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:16.41273+08:00 ERROR [539043,c68056b1a3b3575f] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:07:21.41085+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.164405ms 2023-05-18T13:07:21.41092+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:21.411+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.214622ms 2023-05-18T13:07:21.41103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:26.4042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.432934ms 2023-05-18T13:07:26.40427+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:26.41197+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.509222ms 2023-05-18T13:07:26.41202+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:31.40306+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.074017ms 2023-05-18T13:07:31.40313+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:31.40893+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.302007ms 2023-05-18T13:07:31.40898+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:36.41029+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.122504ms 2023-05-18T13:07:36.41036+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:36.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.08842ms 2023-05-18T13:07:36.41046+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:41.41018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.824201ms 2023-05-18T13:07:41.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:41.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.907518ms 2023-05-18T13:07:41.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:46.41379+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.969506ms 2023-05-18T13:07:46.41385+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:46.42965+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.375611ms 2023-05-18T13:07:46.42971+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:46.46696+08:00 ERROR [539043,b2462fab4a7d89f8] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:07:51.40311+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.120331ms 2023-05-18T13:07:51.40319+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:51.40983+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.265006ms 2023-05-18T13:07:51.40988+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:56.40199+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.846514ms 2023-05-18T13:07:56.40206+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:07:56.40765+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.867002ms 2023-05-18T13:07:56.40769+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:01.41047+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.730899ms 2023-05-18T13:08:01.41054+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:01.41062+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.672715ms 2023-05-18T13:08:01.41065+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:06.41074+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.878101ms 2023-05-18T13:08:06.41082+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:06.41089+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.12572ms 2023-05-18T13:08:06.41092+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:11.41074+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.949602ms 2023-05-18T13:08:11.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:11.41087+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.013519ms 2023-05-18T13:08:11.4109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:16.40283+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.819213ms 2023-05-18T13:08:16.40289+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:16.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.699499ms 2023-05-18T13:08:16.41068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:16.41139+08:00 ERROR [539043,9f85cc25c537b683] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:08:21.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.107804ms 2023-05-18T13:08:21.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:21.41059+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.161921ms 2023-05-18T13:08:21.41063+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:26.40921+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.225896ms 2023-05-18T13:08:26.40928+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:26.41074+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.147705ms 2023-05-18T13:08:26.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:31.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.138205ms 2023-05-18T13:08:31.41052+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:31.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.06682ms 2023-05-18T13:08:31.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:36.40841+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.089795ms 2023-05-18T13:08:36.40847+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:36.40983+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.804901ms 2023-05-18T13:08:36.40991+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:41.41015+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.866501ms 2023-05-18T13:08:41.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:41.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.142121ms 2023-05-18T13:08:41.41036+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:46.42467+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.640498ms 2023-05-18T13:08:46.42473+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:46.43661+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=28.755271ms 2023-05-18T13:08:46.43666+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:46.45142+08:00 ERROR [539043,b10107a7297cde6d] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:08:46.48042+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 1356143 fields: error="open /proc/1356143/status: no such file or directory" 2023-05-18T13:08:51.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.918402ms 2023-05-18T13:08:51.41053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:51.41062+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.621114ms 2023-05-18T13:08:51.41065+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:56.408+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.694789ms 2023-05-18T13:08:56.40807+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:08:56.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.367408ms 2023-05-18T13:08:56.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:01.41119+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.375308ms 2023-05-18T13:09:01.41126+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:01.41135+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.462625ms 2023-05-18T13:09:01.41138+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:06.41059+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.877201ms 2023-05-18T13:09:06.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:06.41074+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.948518ms 2023-05-18T13:09:06.41077+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:11.4036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.970929ms 2023-05-18T13:09:11.40367+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:11.41066+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.389234ms 2023-05-18T13:09:11.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:16.40316+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.177118ms 2023-05-18T13:09:16.40322+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:16.41118+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.923302ms 2023-05-18T13:09:16.41123+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:16.41192+08:00 ERROR [539043,1e1fc830170118d9] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:09:21.40932+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.712302ms 2023-05-18T13:09:21.40941+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:21.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.052104ms 2023-05-18T13:09:21.41044+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:26.41084+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.078604ms 2023-05-18T13:09:26.41093+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:26.411+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.396224ms 2023-05-18T13:09:26.41103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:31.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.259506ms 2023-05-18T13:09:31.41059+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:31.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.244223ms 2023-05-18T13:09:31.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:36.41125+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.964903ms 2023-05-18T13:09:36.41132+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:36.41142+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.026132ms 2023-05-18T13:09:36.41145+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:41.40312+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.132131ms 2023-05-18T13:09:41.40318+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:41.41013+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.053604ms 2023-05-18T13:09:41.41018+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:46.43486+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=27.059349ms 2023-05-18T13:09:46.43493+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:46.43501+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.700844ms 2023-05-18T13:09:46.43504+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:46.46016+08:00 ERROR [539043,bb0bde3ef5f41fce] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:09:51.41328+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.33325ms 2023-05-18T13:09:51.41335+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:51.41347+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.394308ms 2023-05-18T13:09:51.41352+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:56.40966+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.30621ms 2023-05-18T13:09:56.40975+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:09:56.41008+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.129105ms 2023-05-18T13:09:56.41013+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:01.41324+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.450151ms 2023-05-18T13:10:01.41331+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:01.41383+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.174444ms 2023-05-18T13:10:01.41388+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:06.40786+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.244283ms 2023-05-18T13:10:06.40827+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:06.41293+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.471135ms 2023-05-18T13:10:06.41298+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:11.41362+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=20.097059ms 2023-05-18T13:10:11.41369+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:11.41464+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.292459ms 2023-05-18T13:10:11.41469+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:16.40278+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.775726ms 2023-05-18T13:10:16.40285+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:16.41157+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.624811ms 2023-05-18T13:10:16.41163+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:16.41236+08:00 ERROR [539043,6b15d9cf7c5f556e] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:10:16.48086+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields:, module=monitor.ob, duration="29.1µs" 2023-05-18T13:10:16.48093+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields: module=monitor.ob, eventType=add, duration="6µs" 2023-05-18T13:10:16.48096+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields: module=monitor.ob, duration="12.5µs" 2023-05-18T13:10:16.481+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields:, module=monitor.ob, eventType=add, duration="4.8µs" 2023-05-18T13:10:16.48103+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T13:10:16.48473+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc000276820 0xc0002768c0 0xc000276960 0xc000276a00 0xc000276aa0 0xc000276b40 0xc000276be0 0xc000276c80 0xc000276d20 0xc000276dc0 0xc000276e60 0xc000276f00 0xc000276fa0 0xc000277040 0xc0002770e0 0xc000277180 0xc000277220 0xc0002772c0 0xc000277360 0xc000277400 0xc0002774a0 0xc000277540 0xc0002775e0 0xc000277680 0xc000277720 0xc0002777c0 0xc000277860 0xc000277900 0xc0002779a0 0xc000277a40 0xc000277ae0] CollectInterval:1s TimeAlign:false} 2023-05-18T13:10:16.48555+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T13:10:16.48559+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields: duration="5µs", input=mysqlTableInput 2023-05-18T13:10:16.48562+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields:, input=mysqlTableInput, duration="33.2µs" 2023-05-18T13:10:16.48564+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields:, module=monitor.ob, eventType=add, error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)", duration=4.64846ms 2023-05-18T13:10:16.48566+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields: module=monitor.ob, eventType=add, duration=4.66626ms 2023-05-18T13:10:16.48568+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields: duration=4.728961ms, module=monitor.ob 2023-05-18T13:10:16.48569+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields: duration=4.766861ms, module=monitor.ob, eventType=add 2023-05-18T13:10:16.4857+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields:, module=monitor.ob, duration=4.868363ms 2023-05-18T13:10:16.48572+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 16 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T13:10:21.41321+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.521452ms 2023-05-18T13:10:21.41328+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:21.4158+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.541374ms 2023-05-18T13:10:21.41584+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:26.40607+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.609763ms 2023-05-18T13:10:26.40615+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:26.41457+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.669611ms 2023-05-18T13:10:26.41463+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:31.41076+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.716399ms 2023-05-18T13:10:31.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:31.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.929718ms 2023-05-18T13:10:31.41094+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:36.40193+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.952215ms 2023-05-18T13:10:36.40199+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:36.40787+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.273107ms 2023-05-18T13:10:36.40791+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:41.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.900018ms 2023-05-18T13:10:41.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:41.41085+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.489409ms 2023-05-18T13:10:41.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:46.40524+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.946516ms 2023-05-18T13:10:46.4053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:46.41298+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.636198ms 2023-05-18T13:10:46.41303+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:46.44861+08:00 ERROR [539043,a71055578a0200c5] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:10:51.41214+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.034503ms 2023-05-18T13:10:51.4122+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:51.41231+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.312336ms 2023-05-18T13:10:51.41234+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:56.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.862501ms 2023-05-18T13:10:56.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:10:56.41048+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.002919ms 2023-05-18T13:10:56.41052+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:01.41098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.435908ms 2023-05-18T13:11:01.41107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:01.41114+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.829329ms 2023-05-18T13:11:01.41117+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:06.40836+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.395798ms 2023-05-18T13:11:06.40843+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:06.41181+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.008229ms 2023-05-18T13:11:06.41186+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:11.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.966503ms 2023-05-18T13:11:11.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:11.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.757416ms 2023-05-18T13:11:11.41052+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:16.40214+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.924315ms 2023-05-18T13:11:16.40229+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:16.41016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.8174ms 2023-05-18T13:11:16.41021+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:16.41093+08:00 ERROR [539043,5fa1543d23be5bd2] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:11:21.41105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.446509ms 2023-05-18T13:11:21.41113+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:21.4117+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.093333ms 2023-05-18T13:11:21.41175+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:26.40188+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.915615ms 2023-05-18T13:11:26.40194+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:26.40877+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.228706ms 2023-05-18T13:11:26.40882+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:31.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.889602ms 2023-05-18T13:11:31.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:31.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.880617ms 2023-05-18T13:11:31.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:36.41173+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.638911ms 2023-05-18T13:11:36.4118+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:36.41188+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.64764ms 2023-05-18T13:11:36.41192+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:41.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.836401ms 2023-05-18T13:11:41.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:41.41071+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.948719ms 2023-05-18T13:11:41.41074+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:46.42848+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.428299ms 2023-05-18T13:11:46.42857+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:46.42865+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.766816ms 2023-05-18T13:11:46.42868+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:46.44369+08:00 ERROR [539043,740b499e1ecc8495] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:11:51.4133+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.258548ms 2023-05-18T13:11:51.41345+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:51.41444+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.706713ms 2023-05-18T13:11:51.41449+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:56.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.190205ms 2023-05-18T13:11:56.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:11:56.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.178221ms 2023-05-18T13:11:56.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:01.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.312107ms 2023-05-18T13:12:01.41034+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:01.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.094321ms 2023-05-18T13:12:01.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:06.40257+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.087018ms 2023-05-18T13:12:06.40266+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:06.41249+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.973654ms 2023-05-18T13:12:06.41255+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:11.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.150505ms 2023-05-18T13:12:11.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:11.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.511326ms 2023-05-18T13:12:11.41094+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:16.40287+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.132818ms 2023-05-18T13:12:16.40295+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:16.41095+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.922102ms 2023-05-18T13:12:16.411+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:16.41146+08:00 ERROR [539043,4dacf463afe24c29] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:12:21.41118+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.729929ms 2023-05-18T13:12:21.41124+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:21.41129+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.597511ms 2023-05-18T13:12:21.41133+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:26.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.248307ms 2023-05-18T13:12:26.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:26.41093+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.07162ms 2023-05-18T13:12:26.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:31.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.219606ms 2023-05-18T13:12:31.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:31.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.127021ms 2023-05-18T13:12:31.41053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:36.41176+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.664212ms 2023-05-18T13:12:36.41185+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:36.41194+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.929931ms 2023-05-18T13:12:36.41197+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:41.41085+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.083204ms 2023-05-18T13:12:41.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:41.41098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.327824ms 2023-05-18T13:12:41.41101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:46.43469+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=27.039948ms 2023-05-18T13:12:46.43475+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:46.46076+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=26.631543ms 2023-05-18T13:12:46.46082+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:46.46539+08:00 ERROR [539043,15eb62da737df928] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:12:51.41018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.115904ms 2023-05-18T13:12:51.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:51.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.752216ms 2023-05-18T13:12:51.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:56.40665+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.503674ms 2023-05-18T13:12:56.40674+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:12:56.41026+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.273106ms 2023-05-18T13:12:56.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:01.40601+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.064055ms 2023-05-18T13:13:01.40607+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:01.41441+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.297807ms 2023-05-18T13:13:01.41446+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:06.40179+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.830014ms 2023-05-18T13:13:06.40185+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:06.40753+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.959403ms 2023-05-18T13:13:06.40759+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:11.40634+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.715464ms 2023-05-18T13:13:11.40639+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:11.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.777201ms 2023-05-18T13:13:11.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:16.40237+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.722512ms 2023-05-18T13:13:16.40243+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:16.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.808901ms 2023-05-18T13:13:16.41031+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:16.41114+08:00 ERROR [539043,ecb8b0a517c31f35] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:13:21.40247+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.593611ms 2023-05-18T13:13:21.40254+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:21.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.826901ms 2023-05-18T13:13:21.41046+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:26.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.505812ms 2023-05-18T13:13:26.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:26.41047+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.956902ms 2023-05-18T13:13:26.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:31.41054+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.906302ms 2023-05-18T13:13:31.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:31.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.894518ms 2023-05-18T13:13:31.41073+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:36.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.236806ms 2023-05-18T13:13:36.41081+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:36.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.159322ms 2023-05-18T13:13:36.41094+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:41.40579+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.799564ms 2023-05-18T13:13:41.40587+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:41.40963+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.983703ms 2023-05-18T13:13:41.40968+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:46.41566+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.780514ms 2023-05-18T13:13:46.41572+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:46.41734+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.938741ms 2023-05-18T13:13:46.4174+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:46.43226+08:00 ERROR [539043,4d4725d088a0d22d] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:13:51.41+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.182506ms 2023-05-18T13:13:51.41007+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:51.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.00472ms 2023-05-18T13:13:51.4102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:56.4099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.052404ms 2023-05-18T13:13:56.40996+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:13:56.41006+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.763616ms 2023-05-18T13:13:56.4101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:01.40403+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.341233ms 2023-05-18T13:14:01.4041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:01.41093+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.247506ms 2023-05-18T13:14:01.41103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:06.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.184206ms 2023-05-18T13:14:06.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:06.41065+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.040519ms 2023-05-18T13:14:06.41068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:11.41083+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.150905ms 2023-05-18T13:14:11.4109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:11.41101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.126721ms 2023-05-18T13:14:11.41105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:16.40269+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.760313ms 2023-05-18T13:14:16.40276+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:16.41136+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.56251ms 2023-05-18T13:14:16.41141+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:16.41212+08:00 ERROR [539043,0746ecdc38f62777] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:14:21.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.963302ms 2023-05-18T13:14:21.41041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:21.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.185521ms 2023-05-18T13:14:21.41052+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:26.40278+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.916515ms 2023-05-18T13:14:26.40284+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:26.40836+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.939403ms 2023-05-18T13:14:26.40844+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:31.4033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.205331ms 2023-05-18T13:14:31.40336+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:31.40952+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.953202ms 2023-05-18T13:14:31.40959+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:36.41102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.49631ms 2023-05-18T13:14:36.41109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:36.41118+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.430625ms 2023-05-18T13:14:36.41121+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:41.40589+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.216957ms 2023-05-18T13:14:41.40595+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:41.41084+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.404108ms 2023-05-18T13:14:41.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:46.43485+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=26.470541ms 2023-05-18T13:14:46.43491+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:46.43497+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=27.067049ms 2023-05-18T13:14:46.43499+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:46.46271+08:00 ERROR [539043,c4cd4f181dbb8c52] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:14:51.41055+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.094604ms 2023-05-18T13:14:51.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:51.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.123421ms 2023-05-18T13:14:51.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:56.40304+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.010816ms 2023-05-18T13:14:56.4031+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:14:56.40861+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.015103ms 2023-05-18T13:14:56.40866+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:01.41084+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.333108ms 2023-05-18T13:15:01.41092+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:01.41103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.376824ms 2023-05-18T13:15:01.41106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:06.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.049604ms 2023-05-18T13:15:06.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:06.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.794317ms 2023-05-18T13:15:06.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:11.40976+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.904801ms 2023-05-18T13:15:11.40982+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:11.40989+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.660315ms 2023-05-18T13:15:11.40992+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:16.40301+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.194018ms 2023-05-18T13:15:16.40307+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:16.41139+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.284906ms 2023-05-18T13:15:16.41145+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:16.41211+08:00 ERROR [539043,8615284b4f497dd9] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:15:21.41037+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.047004ms 2023-05-18T13:15:21.41044+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:21.41054+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.143421ms 2023-05-18T13:15:21.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:26.4048+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.139343ms 2023-05-18T13:15:26.40486+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:26.41076+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.118805ms 2023-05-18T13:15:26.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:31.41014+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.213006ms 2023-05-18T13:15:31.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:31.41028+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.333924ms 2023-05-18T13:15:31.41031+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:36.41008+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.146705ms 2023-05-18T13:15:36.41014+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:36.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.06892ms 2023-05-18T13:15:36.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:41.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.118905ms 2023-05-18T13:15:41.4106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:41.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.976819ms 2023-05-18T13:15:41.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:46.40924+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.267632ms 2023-05-18T13:15:46.4093+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:46.42578+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.034136ms 2023-05-18T13:15:46.42584+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:46.4261+08:00 ERROR [539043,8a6eda052b8d7083] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:15:51.4091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.683999ms 2023-05-18T13:15:51.40916+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:51.4093+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.064308ms 2023-05-18T13:15:51.40934+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:56.40979+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.994503ms 2023-05-18T13:15:56.40985+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:15:56.40992+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.638414ms 2023-05-18T13:15:56.40995+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:01.40542+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.272658ms 2023-05-18T13:16:01.40549+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:01.40947+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.643098ms 2023-05-18T13:16:01.40952+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:06.41051+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.157205ms 2023-05-18T13:16:06.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:06.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.883318ms 2023-05-18T13:16:06.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:11.40534+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.835753ms 2023-05-18T13:16:11.4054+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:11.4135+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.056704ms 2023-05-18T13:16:11.41357+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:16.40278+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.090617ms 2023-05-18T13:16:16.40284+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:16.41107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.186606ms 2023-05-18T13:16:16.41111+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:16.41181+08:00 ERROR [539043,e1a4d8d0f07e6691] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:16:21.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.341208ms 2023-05-18T13:16:21.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:21.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.322124ms 2023-05-18T13:16:21.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:26.41023+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.677699ms 2023-05-18T13:16:26.41029+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:26.41036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.890117ms 2023-05-18T13:16:26.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:31.4108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.866202ms 2023-05-18T13:16:31.41087+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:31.41095+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.04332ms 2023-05-18T13:16:31.41098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:36.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.068204ms 2023-05-18T13:16:36.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:36.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.787417ms 2023-05-18T13:16:36.41053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:41.41096+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.113505ms 2023-05-18T13:16:41.41105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:41.41114+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.188822ms 2023-05-18T13:16:41.41117+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:46.40857+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.417147ms 2023-05-18T13:16:46.40865+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:46.41672+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.022904ms 2023-05-18T13:16:46.41677+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:46.45239+08:00 ERROR [539043,82904fb760851664] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:16:51.41171+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.727528ms 2023-05-18T13:16:51.41177+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:51.41183+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.314707ms 2023-05-18T13:16:51.41187+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:56.40315+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.141531ms 2023-05-18T13:16:56.40324+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:16:56.41126+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.958602ms 2023-05-18T13:16:56.41132+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:01.40972+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.932402ms 2023-05-18T13:17:01.40979+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:01.40987+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.695515ms 2023-05-18T13:17:01.4099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:06.41016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.977403ms 2023-05-18T13:17:06.41023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:06.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.104421ms 2023-05-18T13:17:06.41036+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:11.40204+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.053317ms 2023-05-18T13:17:11.4021+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:11.40783+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.133005ms 2023-05-18T13:17:11.4079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:16.40234+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.737813ms 2023-05-18T13:17:16.40241+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:16.41037+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.916802ms 2023-05-18T13:17:16.41043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:16.41114+08:00 ERROR [539043,64a8bfa1a39454bd] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:17:21.41055+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.961202ms 2023-05-18T13:17:21.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:21.41071+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.144721ms 2023-05-18T13:17:21.41075+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:26.41098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.770913ms 2023-05-18T13:17:26.41104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:26.41112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.879531ms 2023-05-18T13:17:26.41116+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:31.41028+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.163105ms 2023-05-18T13:17:31.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:31.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.08262ms 2023-05-18T13:17:31.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:36.40991+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.100705ms 2023-05-18T13:17:36.40997+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:36.41004+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.956918ms 2023-05-18T13:17:36.41009+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:41.40786+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.213983ms 2023-05-18T13:17:41.40793+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:41.41189+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.161605ms 2023-05-18T13:17:41.41194+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:46.41676+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.141618ms 2023-05-18T13:17:46.41683+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:46.42535+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.427009ms 2023-05-18T13:17:46.42539+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:46.4517+08:00 ERROR [539043,3ad43ce1c7978234] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:17:51.41008+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.641999ms 2023-05-18T13:17:51.41014+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:51.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.244109ms 2023-05-18T13:17:51.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:56.41324+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.952657ms 2023-05-18T13:17:56.41333+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:17:56.41342+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.912341ms 2023-05-18T13:17:56.41345+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:01.4042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.162931ms 2023-05-18T13:18:01.40428+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:01.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.7397ms 2023-05-18T13:18:01.41075+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:06.41099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.170405ms 2023-05-18T13:18:06.41105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:06.41112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.252123ms 2023-05-18T13:18:06.41115+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:11.41323+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.225748ms 2023-05-18T13:18:11.41329+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:11.41362+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.908041ms 2023-05-18T13:18:11.41368+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:16.40226+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.749412ms 2023-05-18T13:18:16.40232+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:16.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.063903ms 2023-05-18T13:18:16.41048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:16.41164+08:00 ERROR [539043,a9bd91df4c6923c7] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:18:21.41028+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.811801ms 2023-05-18T13:18:21.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:21.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.729116ms 2023-05-18T13:18:21.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:26.41055+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.178606ms 2023-05-18T13:18:26.41065+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:26.41074+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.228422ms 2023-05-18T13:18:26.41076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:31.40212+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.635411ms 2023-05-18T13:18:31.4022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:31.40807+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.230106ms 2023-05-18T13:18:31.40813+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:36.41026+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.929902ms 2023-05-18T13:18:36.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:36.41104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.777229ms 2023-05-18T13:18:36.41108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:41.40216+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.683212ms 2023-05-18T13:18:41.40221+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:41.41041+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.142305ms 2023-05-18T13:18:41.41046+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:46.42299+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.836301ms 2023-05-18T13:18:46.42305+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:46.42312+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.715415ms 2023-05-18T13:18:46.42315+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:46.47639+08:00 ERROR [539043,9141782e1d19b360] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:18:51.40972+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.463897ms 2023-05-18T13:18:51.40978+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:51.40985+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.089007ms 2023-05-18T13:18:51.40988+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:56.41002+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.735199ms 2023-05-18T13:18:56.41008+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:18:56.41015+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.773816ms 2023-05-18T13:18:56.41019+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:01.40782+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.656889ms 2023-05-18T13:19:01.40791+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:01.40968+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.821201ms 2023-05-18T13:19:01.40972+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:06.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.978103ms 2023-05-18T13:19:06.41086+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:06.41097+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.128321ms 2023-05-18T13:19:06.41101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:11.40343+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.339033ms 2023-05-18T13:19:11.40349+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:11.4082+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.501509ms 2023-05-18T13:19:11.40825+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:16.40196+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.618811ms 2023-05-18T13:19:16.40203+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:16.41022+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.145505ms 2023-05-18T13:19:16.41027+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:16.41138+08:00 ERROR [539043,52dad7d671ccc0bb] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:19:21.40192+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.669711ms 2023-05-18T13:19:21.40198+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:21.40854+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.413609ms 2023-05-18T13:19:21.40861+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:26.41107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.118705ms 2023-05-18T13:19:26.41114+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:26.41121+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.08432ms 2023-05-18T13:19:26.41125+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:31.40168+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.710612ms 2023-05-18T13:19:31.40174+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:31.4088+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.187706ms 2023-05-18T13:19:31.40885+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:36.41295+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.7817ms 2023-05-18T13:19:36.41301+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:36.4131+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.264048ms 2023-05-18T13:19:36.41314+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:41.40217+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.574211ms 2023-05-18T13:19:41.40223+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:41.40834+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.184405ms 2023-05-18T13:19:41.40839+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:46.4161+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.164621ms 2023-05-18T13:19:46.41617+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:46.43085+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.4892ms 2023-05-18T13:19:46.43091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:46.45307+08:00 ERROR [539043,ee235a57add14c31] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:19:51.40963+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.819001ms 2023-05-18T13:19:51.40969+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:51.40976+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.500113ms 2023-05-18T13:19:51.40979+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:56.40196+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.54061ms 2023-05-18T13:19:56.40203+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:19:56.40969+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.633599ms 2023-05-18T13:19:56.40974+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:01.40311+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.112631ms 2023-05-18T13:20:01.40319+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:01.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.230106ms 2023-05-18T13:20:01.41036+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:06.41109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.59021ms 2023-05-18T13:20:06.41115+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:06.41123+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.736328ms 2023-05-18T13:20:06.41127+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:11.41135+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.901015ms 2023-05-18T13:20:11.41141+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:11.4115+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.836929ms 2023-05-18T13:20:11.41153+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:16.40315+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.05513ms 2023-05-18T13:20:16.40321+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:16.41119+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.947702ms 2023-05-18T13:20:16.41124+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:16.41193+08:00 ERROR [539043,917ba1852421883c] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:20:16.48633+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields: duration="35.7µs", module=monitor.ob 2023-05-18T13:20:16.48641+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields:, eventType=add, module=monitor.ob, duration="5.4µs" 2023-05-18T13:20:16.48643+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields:, module=monitor.ob, duration="4µs" 2023-05-18T13:20:16.48647+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields: duration="4.5µs", module=monitor.ob, eventType=add 2023-05-18T13:20:16.48651+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T13:20:16.49321+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc0006a48c0 0xc0006a4960 0xc0006a4a00 0xc0006a4aa0 0xc0006a4b40 0xc0006a4be0 0xc0006a4c80 0xc0006a4d20 0xc0006a4dc0 0xc0006a4e60 0xc0006a4f00 0xc0006a4fa0 0xc0006a5040 0xc0006a50e0 0xc0006a5180 0xc0006a5220 0xc0006a52c0 0xc0006a5360 0xc0006a5400 0xc0006a54a0 0xc0006a5540 0xc0006a55e0 0xc0006a5680 0xc0006a5720 0xc0006a57c0 0xc0006a5860 0xc0006a5900 0xc0006a59a0 0xc0006a5a40 0xc0006a5ae0 0xc0006a5b80] CollectInterval:1s TimeAlign:false} 2023-05-18T13:20:16.49602+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T13:20:16.49605+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields: duration="4µs", input=mysqlTableInput 2023-05-18T13:20:16.49606+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields: duration="22.7µs", input=mysqlTableInput 2023-05-18T13:20:16.49609+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields:, module=monitor.ob, eventType=add, error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)", duration=9.617724ms 2023-05-18T13:20:16.49614+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields:, eventType=add, module=monitor.ob, duration=9.668024ms 2023-05-18T13:20:16.49616+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields:, module=monitor.ob, duration=9.737826ms 2023-05-18T13:20:16.49618+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields:, module=monitor.ob, eventType=add, duration=9.775326ms 2023-05-18T13:20:16.49619+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields:, module=monitor.ob, duration=9.888627ms 2023-05-18T13:20:16.49622+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 17 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T13:20:21.4102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.778701ms 2023-05-18T13:20:21.41027+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:21.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.538413ms 2023-05-18T13:20:21.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:26.40697+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.581275ms 2023-05-18T13:20:26.40705+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:26.41037+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.242407ms 2023-05-18T13:20:26.41044+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:31.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.210706ms 2023-05-18T13:20:31.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:31.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.251123ms 2023-05-18T13:20:31.41048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:36.4023+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.964615ms 2023-05-18T13:20:36.40237+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:36.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.930202ms 2023-05-18T13:20:36.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:41.41029+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.04342ms 2023-05-18T13:20:41.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:41.41041+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.402609ms 2023-05-18T13:20:41.41044+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:46.41383+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.894715ms 2023-05-18T13:20:46.41389+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:46.43102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=25.58983ms 2023-05-18T13:20:46.43109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:46.44739+08:00 ERROR [539043,29d3c45d5a52c090] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:20:51.41089+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.468509ms 2023-05-18T13:20:51.41095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:51.41104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.394325ms 2023-05-18T13:20:51.41107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:56.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.49241ms 2023-05-18T13:20:56.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:20:56.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.624727ms 2023-05-18T13:20:56.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:01.4097+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.33351ms 2023-05-18T13:21:01.40976+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:01.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.922402ms 2023-05-18T13:21:01.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:06.41103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.190905ms 2023-05-18T13:21:06.41109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:06.41116+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.183122ms 2023-05-18T13:21:06.41119+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:11.41084+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.201306ms 2023-05-18T13:21:11.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:11.41099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.764329ms 2023-05-18T13:21:11.41102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:16.40296+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.054817ms 2023-05-18T13:21:16.40311+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:16.41148+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.330408ms 2023-05-18T13:21:16.41153+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:16.4122+08:00 ERROR [539043,10227944e051ff42] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:21:21.41047+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.293023ms 2023-05-18T13:21:21.41055+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:21.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.412409ms 2023-05-18T13:21:21.41066+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:26.41064+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.142105ms 2023-05-18T13:21:26.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:26.41078+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.183221ms 2023-05-18T13:21:26.41081+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:31.41125+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.832814ms 2023-05-18T13:21:31.41132+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:31.41139+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.789329ms 2023-05-18T13:21:31.41142+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:36.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.972403ms 2023-05-18T13:21:36.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:36.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.725816ms 2023-05-18T13:21:36.41048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:41.41054+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.165705ms 2023-05-18T13:21:41.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:41.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.278022ms 2023-05-18T13:21:41.41076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:46.41462+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.774512ms 2023-05-18T13:21:46.41469+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:46.43778+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=23.024294ms 2023-05-18T13:21:46.43784+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:46.45668+08:00 ERROR [539043,6d98c7cff511c028] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:21:51.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.668098ms 2023-05-18T13:21:51.41029+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:51.41036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.772014ms 2023-05-18T13:21:51.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:56.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.773499ms 2023-05-18T13:21:56.41052+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:21:56.41066+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.768514ms 2023-05-18T13:21:56.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:01.41182+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.144104ms 2023-05-18T13:22:01.41188+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:01.41195+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.076831ms 2023-05-18T13:22:01.41199+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:06.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.195905ms 2023-05-18T13:22:06.41073+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:06.41092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.24082ms 2023-05-18T13:22:06.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:11.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.997902ms 2023-05-18T13:22:11.41053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:11.41062+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.888716ms 2023-05-18T13:22:11.41066+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:16.40298+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.263718ms 2023-05-18T13:22:16.40305+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:16.41111+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.030502ms 2023-05-18T13:22:16.41116+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:16.41238+08:00 ERROR [539043,fa147053ff45886c] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:22:21.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.942602ms 2023-05-18T13:22:21.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:21.41092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.926816ms 2023-05-18T13:22:21.41095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:26.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.059403ms 2023-05-18T13:22:26.41083+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:26.41092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.949017ms 2023-05-18T13:22:26.41095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:31.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.965416ms 2023-05-18T13:22:31.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:31.41076+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.376007ms 2023-05-18T13:22:31.41083+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:36.41016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.207705ms 2023-05-18T13:22:36.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:36.41029+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.114418ms 2023-05-18T13:22:36.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:41.41262+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.38632ms 2023-05-18T13:22:41.4127+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:41.41276+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.674551ms 2023-05-18T13:22:41.41279+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:46.41568+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.214017ms 2023-05-18T13:22:46.41575+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:46.42408+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.252805ms 2023-05-18T13:22:46.42414+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:46.45691+08:00 ERROR [539043,32c8b39ac0d47106] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:22:51.40973+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.941501ms 2023-05-18T13:22:51.40979+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:51.40987+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.590712ms 2023-05-18T13:22:51.4099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:56.4107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.003703ms 2023-05-18T13:22:56.41077+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:22:56.41087+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.124619ms 2023-05-18T13:22:56.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:01.41112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.464708ms 2023-05-18T13:23:01.41119+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:01.41126+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.879228ms 2023-05-18T13:23:01.41129+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:06.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.140704ms 2023-05-18T13:23:06.41041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:06.41048+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.972817ms 2023-05-18T13:23:06.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:11.40984+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.171605ms 2023-05-18T13:23:11.40993+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:11.41002+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.886116ms 2023-05-18T13:23:11.41004+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:16.40216+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.802113ms 2023-05-18T13:23:16.40223+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:16.41008+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.8147ms 2023-05-18T13:23:16.41015+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:16.41117+08:00 ERROR [539043,21cc402d4fe51302] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:23:21.4102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.781699ms 2023-05-18T13:23:21.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:21.41036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.841915ms 2023-05-18T13:23:21.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:26.41128+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.174004ms 2023-05-18T13:23:26.41135+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:26.41143+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.455223ms 2023-05-18T13:23:26.41145+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:31.40937+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.533598ms 2023-05-18T13:23:31.40943+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:31.41121+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.126004ms 2023-05-18T13:23:31.41126+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:36.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.913101ms 2023-05-18T13:23:36.41033+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:36.41041+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.999817ms 2023-05-18T13:23:36.41044+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:41.41084+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.409707ms 2023-05-18T13:23:41.4109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:41.41098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.740727ms 2023-05-18T13:23:41.411+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:46.41688+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.703911ms 2023-05-18T13:23:46.41694+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:46.43733+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=29.662878ms 2023-05-18T13:23:46.4374+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:46.4375+08:00 ERROR [539043,20c5acdb4835b742] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:23:46.46536+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 1458991 fields: error="open /proc/1458991/status: no such file or directory" 2023-05-18T13:23:51.41064+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.866801ms 2023-05-18T13:23:51.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:51.41081+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.075018ms 2023-05-18T13:23:51.41086+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:56.41041+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.150804ms 2023-05-18T13:23:56.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:23:56.41055+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.187619ms 2023-05-18T13:23:56.41059+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:01.41+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.105703ms 2023-05-18T13:24:01.41006+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:01.41012+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.891416ms 2023-05-18T13:24:01.41015+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:06.40985+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.8786ms 2023-05-18T13:24:06.40992+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:06.41+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.804014ms 2023-05-18T13:24:06.41003+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:11.4112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.550109ms 2023-05-18T13:24:11.41126+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:11.41135+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.786226ms 2023-05-18T13:24:11.41138+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:16.4023+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.050816ms 2023-05-18T13:24:16.40237+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:16.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.266306ms 2023-05-18T13:24:16.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:16.41141+08:00 ERROR [539043,8c2b306180b79278] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:24:21.40152+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.533209ms 2023-05-18T13:24:21.4016+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:21.40875+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.137604ms 2023-05-18T13:24:21.4088+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:26.40591+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.436259ms 2023-05-18T13:24:26.40597+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:26.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.026302ms 2023-05-18T13:24:26.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:31.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.185204ms 2023-05-18T13:24:31.41059+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:31.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.037018ms 2023-05-18T13:24:31.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:36.40356+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.254131ms 2023-05-18T13:24:36.40364+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:36.41006+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.8171ms 2023-05-18T13:24:36.41012+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:41.41126+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.389607ms 2023-05-18T13:24:41.41132+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:41.4114+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.483223ms 2023-05-18T13:24:41.41143+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:46.42455+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.869916ms 2023-05-18T13:24:46.42464+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:46.4247+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.515411ms 2023-05-18T13:24:46.42473+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:46.46405+08:00 ERROR [539043,33b1812629012b1c] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:24:51.40169+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.705311ms 2023-05-18T13:24:51.40177+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:51.40749+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.876901ms 2023-05-18T13:24:51.40754+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:56.40706+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.795176ms 2023-05-18T13:24:56.40713+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:24:56.41025+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.147404ms 2023-05-18T13:24:56.4103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:01.41109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.148604ms 2023-05-18T13:25:01.41116+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:01.41127+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.383922ms 2023-05-18T13:25:01.41131+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:06.40197+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.936814ms 2023-05-18T13:25:06.40206+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:06.41037+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.250506ms 2023-05-18T13:25:06.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:11.4113+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.358321ms 2023-05-18T13:25:11.41137+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:11.41142+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.439008ms 2023-05-18T13:25:11.41145+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:16.40599+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.530047ms 2023-05-18T13:25:16.40606+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:16.41444+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.331506ms 2023-05-18T13:25:16.41449+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:16.41563+08:00 ERROR [539043,a74035732f2e84dd] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:25:21.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.106304ms 2023-05-18T13:25:21.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:21.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.963516ms 2023-05-18T13:25:21.41094+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:26.41094+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.099504ms 2023-05-18T13:25:26.41101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:26.41109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.371422ms 2023-05-18T13:25:26.41112+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:31.41098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.148504ms 2023-05-18T13:25:31.41105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:31.41112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.192919ms 2023-05-18T13:25:31.41115+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:36.40972+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.413009ms 2023-05-18T13:25:36.40979+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:36.41008+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.105304ms 2023-05-18T13:25:36.41012+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:41.40226+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.977815ms 2023-05-18T13:25:41.40232+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:41.40822+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.172104ms 2023-05-18T13:25:41.40827+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:46.42535+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=27.843355ms 2023-05-18T13:25:46.42543+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:46.45345+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=28.647666ms 2023-05-18T13:25:46.45351+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:46.45356+08:00 ERROR [539043,b423ac4a5d48278f] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:25:51.41065+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.268606ms 2023-05-18T13:25:51.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:51.4108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.135619ms 2023-05-18T13:25:51.41083+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:56.41102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.118204ms 2023-05-18T13:25:56.41108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:25:56.41118+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.498624ms 2023-05-18T13:25:56.41121+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:01.41018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.229305ms 2023-05-18T13:26:01.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:01.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.165519ms 2023-05-18T13:26:01.41034+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:06.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.843ms 2023-05-18T13:26:06.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:06.41076+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.751913ms 2023-05-18T13:26:06.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:11.40884+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.458497ms 2023-05-18T13:26:11.40891+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:11.41062+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.321206ms 2023-05-18T13:26:11.41068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:16.40274+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.830513ms 2023-05-18T13:26:16.4028+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:16.41097+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.122104ms 2023-05-18T13:26:16.41104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:16.41182+08:00 ERROR [539043,e89acd5fa9df7970] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:26:21.40204+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.770812ms 2023-05-18T13:26:21.40211+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:21.40795+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.041902ms 2023-05-18T13:26:21.40802+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:26.40253+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.132516ms 2023-05-18T13:26:26.40263+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:26.41188+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.208017ms 2023-05-18T13:26:26.41193+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:31.41065+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.25632ms 2023-05-18T13:26:31.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:31.41076+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.534709ms 2023-05-18T13:26:31.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:36.40264+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.891413ms 2023-05-18T13:26:36.40271+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:36.40866+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.242305ms 2023-05-18T13:26:36.40871+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:41.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.425407ms 2023-05-18T13:26:41.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:41.41094+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.222819ms 2023-05-18T13:26:41.41098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:46.41698+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.103716ms 2023-05-18T13:26:46.41704+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:46.4253+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.174905ms 2023-05-18T13:26:46.42535+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:46.46859+08:00 ERROR [539043,4e87301575c008f1] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:26:51.40216+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.184017ms 2023-05-18T13:26:51.40223+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:51.40883+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.215205ms 2023-05-18T13:26:51.40888+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:56.41094+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.265205ms 2023-05-18T13:26:56.41101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:26:56.41108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.22352ms 2023-05-18T13:26:56.41111+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:01.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.086103ms 2023-05-18T13:27:01.41041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:01.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.046217ms 2023-05-18T13:27:01.41054+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:06.41199+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.200305ms 2023-05-18T13:27:06.41205+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:06.41214+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.518936ms 2023-05-18T13:27:06.41217+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:11.41094+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.240405ms 2023-05-18T13:27:11.411+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:11.41109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.26882ms 2023-05-18T13:27:11.41113+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:16.4025+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.158716ms 2023-05-18T13:27:16.40258+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:16.41185+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.224818ms 2023-05-18T13:27:16.4119+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:16.41261+08:00 ERROR [539043,c17b1eede13c099d] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:27:21.41143+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.713511ms 2023-05-18T13:27:21.41151+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:21.41162+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.193032ms 2023-05-18T13:27:21.41166+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:26.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.8412ms 2023-05-18T13:27:26.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:26.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.936016ms 2023-05-18T13:27:26.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:31.40984+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.913901ms 2023-05-18T13:27:31.40991+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:31.41002+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.742413ms 2023-05-18T13:27:31.41006+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:36.40311+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.110029ms 2023-05-18T13:27:36.40319+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:36.40956+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.8356ms 2023-05-18T13:27:36.40962+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:41.41002+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.715913ms 2023-05-18T13:27:41.41009+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:41.41061+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.479208ms 2023-05-18T13:27:41.41065+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:46.42887+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=27.129146ms 2023-05-18T13:27:46.42895+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:46.42901+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=26.795141ms 2023-05-18T13:27:46.42904+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:46.44975+08:00 ERROR [539043,8729b2f55c414df1] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:27:51.41106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.056302ms 2023-05-18T13:27:51.41114+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:51.41121+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.28742ms 2023-05-18T13:27:51.41124+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:56.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.098903ms 2023-05-18T13:27:56.41081+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:27:56.41092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.159219ms 2023-05-18T13:27:56.41095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:01.40853+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.153093ms 2023-05-18T13:28:01.4086+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:01.41024+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.075803ms 2023-05-18T13:28:01.4103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:06.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.169804ms 2023-05-18T13:28:06.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:06.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.325921ms 2023-05-18T13:28:06.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:11.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.970402ms 2023-05-18T13:28:11.4106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:11.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.999617ms 2023-05-18T13:28:11.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:16.40267+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.071815ms 2023-05-18T13:28:16.40274+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:16.41074+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.967501ms 2023-05-18T13:28:16.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:16.41146+08:00 ERROR [539043,7cef0b7bef849b8b] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:28:21.41135+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.542409ms 2023-05-18T13:28:21.41148+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:21.41169+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.08683ms 2023-05-18T13:28:21.41173+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:26.41088+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.343806ms 2023-05-18T13:28:26.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:26.41104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.21252ms 2023-05-18T13:28:26.41108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:31.40161+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.63041ms 2023-05-18T13:28:31.40168+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:31.40777+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.161804ms 2023-05-18T13:28:31.40783+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:36.41125+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.439808ms 2023-05-18T13:28:36.41131+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:36.4114+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.947729ms 2023-05-18T13:28:36.41146+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:41.41038+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.675297ms 2023-05-18T13:28:41.41048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:41.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.927716ms 2023-05-18T13:28:41.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:46.41669+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.022902ms 2023-05-18T13:28:46.41677+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:46.41685+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.976742ms 2023-05-18T13:28:46.41689+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:46.44917+08:00 ERROR [539043,da8fa47c35248a12] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:28:51.41205+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.324019ms 2023-05-18T13:28:51.41212+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:51.41223+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.670738ms 2023-05-18T13:28:51.41227+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:56.41098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.909514ms 2023-05-18T13:28:56.41104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:28:56.41111+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.784027ms 2023-05-18T13:28:56.41114+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:01.40681+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.689362ms 2023-05-18T13:29:01.40689+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:01.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.823199ms 2023-05-18T13:29:01.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:06.40323+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.265931ms 2023-05-18T13:29:06.4033+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:06.40801+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.314606ms 2023-05-18T13:29:06.40806+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:11.40259+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.912814ms 2023-05-18T13:29:11.40266+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:11.41112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.423708ms 2023-05-18T13:29:11.41116+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:16.40262+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.052815ms 2023-05-18T13:29:16.40269+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:16.41116+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.426107ms 2023-05-18T13:29:16.41121+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:16.41187+08:00 ERROR [539043,08de359c197fb90c] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:29:21.41119+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.163705ms 2023-05-18T13:29:21.41126+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:21.41135+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.420923ms 2023-05-18T13:29:21.41138+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:26.40996+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.015302ms 2023-05-18T13:29:26.41002+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:26.4101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.960917ms 2023-05-18T13:29:26.41013+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:31.40975+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.8669ms 2023-05-18T13:29:31.40982+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:31.40989+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.690413ms 2023-05-18T13:29:31.40992+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:36.40987+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.769ms 2023-05-18T13:29:36.40993+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:36.41002+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.46401ms 2023-05-18T13:29:36.41005+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:41.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.752898ms 2023-05-18T13:29:41.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:41.41055+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.647212ms 2023-05-18T13:29:41.41059+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:46.41381+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.711011ms 2023-05-18T13:29:46.41387+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:46.42203+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.063003ms 2023-05-18T13:29:46.42207+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:46.44832+08:00 ERROR [539043,4ce70fc39d9a987d] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:29:51.41135+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.194804ms 2023-05-18T13:29:51.41141+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:51.41149+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.100631ms 2023-05-18T13:29:51.41152+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:56.41092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.150204ms 2023-05-18T13:29:56.41099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:29:56.41106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.031718ms 2023-05-18T13:29:56.41109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:01.40474+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.054441ms 2023-05-18T13:30:01.4048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:01.40992+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.689398ms 2023-05-18T13:30:01.40997+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:06.40211+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.983714ms 2023-05-18T13:30:06.40217+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:06.41019+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.974402ms 2023-05-18T13:30:06.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:11.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.622025ms 2023-05-18T13:30:11.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:11.41092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.453608ms 2023-05-18T13:30:11.41095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:16.40285+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.916614ms 2023-05-18T13:30:16.4029+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:16.41088+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.937601ms 2023-05-18T13:30:16.41092+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:16.41162+08:00 ERROR [539043,0c43cf473ccc7582] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:30:16.49628+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields: duration="27.401µs", module=monitor.ob 2023-05-18T13:30:16.49635+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields:, eventType=add, module=monitor.ob, duration="5.5µs" 2023-05-18T13:30:16.49637+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields: module=monitor.ob, duration="6.6µs" 2023-05-18T13:30:16.49648+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields: module=monitor.ob, eventType=add, duration="7.5µs" 2023-05-18T13:30:16.49651+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T13:30:16.50024+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc0001f0640 0xc0001f06e0 0xc0001f0780 0xc0001f0820 0xc0001f08c0 0xc0001f0960 0xc0001f0a00 0xc0001f0aa0 0xc0001f0b40 0xc0001f0be0 0xc0001f0c80 0xc0001f0d20 0xc0001f0dc0 0xc0001f0e60 0xc0001f0f00 0xc0001f0fa0 0xc0001f1040 0xc0001f10e0 0xc0001f1180 0xc0001f1220 0xc0001f12c0 0xc0001f1360 0xc0001f1400 0xc0001f14a0 0xc0001f1540 0xc0001f15e0 0xc0001f1680 0xc0001f1720 0xc0001f17c0 0xc0001f1860 0xc0001f1900] CollectInterval:1s TimeAlign:false} 2023-05-18T13:30:16.50108+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T13:30:16.50111+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields:, input=mysqlTableInput, duration="4.701µs" 2023-05-18T13:30:16.50113+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields:, input=mysqlTableInput, duration="23.501µs" 2023-05-18T13:30:16.50116+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields: eventType=add, error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)", duration=4.68336ms, module=monitor.ob 2023-05-18T13:30:16.50119+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields: duration=4.71366ms, module=monitor.ob, eventType=add 2023-05-18T13:30:16.50121+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields: module=monitor.ob, duration=4.846362ms 2023-05-18T13:30:16.50123+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields:, module=monitor.ob, eventType=add, duration=4.884962ms 2023-05-18T13:30:16.50124+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields: module=monitor.ob, duration=4.989864ms 2023-05-18T13:30:16.50126+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 18 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T13:30:21.40178+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.778412ms 2023-05-18T13:30:21.40184+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:21.40763+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.049903ms 2023-05-18T13:30:21.40768+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:26.40539+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.538747ms 2023-05-18T13:30:26.40545+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:26.41082+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.264705ms 2023-05-18T13:30:26.41087+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:31.41059+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.211004ms 2023-05-18T13:30:31.41065+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:31.41074+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.377721ms 2023-05-18T13:30:31.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:36.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.480908ms 2023-05-18T13:30:36.41041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:36.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.452423ms 2023-05-18T13:30:36.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:41.40989+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.8591ms 2023-05-18T13:30:41.40996+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:41.41005+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.594512ms 2023-05-18T13:30:41.41009+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:46.40808+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.345619ms 2023-05-18T13:30:46.40815+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:46.41623+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.042402ms 2023-05-18T13:30:46.41627+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:46.44878+08:00 ERROR [539043,0bd1018602be2340] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:30:51.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.310006ms 2023-05-18T13:30:51.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:51.41087+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.27032ms 2023-05-18T13:30:51.41097+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:56.40243+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.45402ms 2023-05-18T13:30:56.40249+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:30:56.40754+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.917201ms 2023-05-18T13:30:56.40761+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:01.41146+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.078415ms 2023-05-18T13:31:01.41153+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:01.41163+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.424135ms 2023-05-18T13:31:01.41167+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:06.40651+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.182968ms 2023-05-18T13:31:06.40659+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:06.41012+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.8703ms 2023-05-18T13:31:06.41017+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:11.41014+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.273106ms 2023-05-18T13:31:11.41021+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:11.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.279321ms 2023-05-18T13:31:11.41033+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:16.4021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.809312ms 2023-05-18T13:31:16.40216+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:16.41029+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.085703ms 2023-05-18T13:31:16.41034+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:16.41111+08:00 ERROR [539043,415c14e747f43d4e] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:31:21.40289+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.998515ms 2023-05-18T13:31:21.40296+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:21.40868+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.144504ms 2023-05-18T13:31:21.40873+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:26.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.004202ms 2023-05-18T13:31:26.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:26.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.314421ms 2023-05-18T13:31:26.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:31.4094+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.467297ms 2023-05-18T13:31:31.40946+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:31.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.623697ms 2023-05-18T13:31:31.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:36.40257+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.828313ms 2023-05-18T13:31:36.40266+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:36.40861+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.231005ms 2023-05-18T13:31:36.40867+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:41.40939+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.753299ms 2023-05-18T13:31:41.40945+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:41.40953+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.364909ms 2023-05-18T13:31:41.40957+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:46.43114+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.66044ms 2023-05-18T13:31:46.4312+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:46.43126+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=27.278248ms 2023-05-18T13:31:46.43128+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:46.45233+08:00 ERROR [539043,b8f663da5a5f49c5] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:31:51.41036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.190719ms 2023-05-18T13:31:51.41043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:51.41098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.306806ms 2023-05-18T13:31:51.41105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:56.41036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.102303ms 2023-05-18T13:31:56.41045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:31:56.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.660612ms 2023-05-18T13:31:56.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:01.40985+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.163705ms 2023-05-18T13:32:01.40992+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:01.40999+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.839615ms 2023-05-18T13:32:01.41002+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:06.40994+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.8008ms 2023-05-18T13:32:06.41001+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:06.41011+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.562811ms 2023-05-18T13:32:06.41015+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:11.40696+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.830164ms 2023-05-18T13:32:11.40705+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:11.41579+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.699611ms 2023-05-18T13:32:11.41584+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:16.40225+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.903613ms 2023-05-18T13:32:16.40231+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:16.40987+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.517496ms 2023-05-18T13:32:16.40992+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:16.41062+08:00 ERROR [539043,b19ed9e3dae38c00] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:32:21.4099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.772699ms 2023-05-18T13:32:21.40996+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:21.41004+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.576712ms 2023-05-18T13:32:21.41006+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:26.40253+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.900514ms 2023-05-18T13:32:26.40261+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:26.41248+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.081554ms 2023-05-18T13:32:26.41253+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:31.41071+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.084803ms 2023-05-18T13:32:31.41077+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:31.41087+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.920616ms 2023-05-18T13:32:31.4109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:36.41127+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.239305ms 2023-05-18T13:32:36.41134+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:36.41141+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.405822ms 2023-05-18T13:32:36.41145+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:41.41114+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.57601ms 2023-05-18T13:32:41.41121+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:41.4113+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.400322ms 2023-05-18T13:32:41.41133+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:46.42734+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.098554ms 2023-05-18T13:32:46.42769+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:46.4278+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=28.857968ms 2023-05-18T13:32:46.42783+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:46.46501+08:00 ERROR [539043,ce021f753f822b15] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:32:51.40423+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.732737ms 2023-05-18T13:32:51.40429+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:51.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.722199ms 2023-05-18T13:32:51.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:56.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.171304ms 2023-05-18T13:32:56.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:32:56.41102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.217019ms 2023-05-18T13:32:56.41107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:01.41022+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.930301ms 2023-05-18T13:33:01.41028+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:01.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.861815ms 2023-05-18T13:33:01.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:06.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.7791ms 2023-05-18T13:33:06.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:06.41076+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.863515ms 2023-05-18T13:33:06.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:11.40319+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.17713ms 2023-05-18T13:33:11.40327+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:11.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.56011ms 2023-05-18T13:33:11.41075+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:16.40235+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.355319ms 2023-05-18T13:33:16.40242+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:16.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.775399ms 2023-05-18T13:33:16.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:16.41101+08:00 ERROR [539043,ccc73c5db67fd5c4] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:33:21.41038+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.012802ms 2023-05-18T13:33:21.41045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:21.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.835615ms 2023-05-18T13:33:21.4106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:26.41139+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.541309ms 2023-05-18T13:33:26.41146+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:26.41153+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.152331ms 2023-05-18T13:33:26.41156+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:31.41016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.007702ms 2023-05-18T13:33:31.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:31.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.919316ms 2023-05-18T13:33:31.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:36.40769+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.755375ms 2023-05-18T13:33:36.40776+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:36.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.8278ms 2023-05-18T13:33:36.41074+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:41.41231+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.918313ms 2023-05-18T13:33:41.41238+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:41.41248+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.574937ms 2023-05-18T13:33:41.41253+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:46.41526+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.773212ms 2023-05-18T13:33:46.41541+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:46.42367+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.163304ms 2023-05-18T13:33:46.42372+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:46.46686+08:00 ERROR [539043,a29622ce7eca87dc] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:33:51.41104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.368907ms 2023-05-18T13:33:51.41111+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:51.41119+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.557624ms 2023-05-18T13:33:51.41122+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:56.41327+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.64125ms 2023-05-18T13:33:56.41336+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:33:56.41574+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.719411ms 2023-05-18T13:33:56.41579+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:01.41123+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.212904ms 2023-05-18T13:34:01.4113+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:01.41137+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.693325ms 2023-05-18T13:34:01.4114+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:06.41319+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.885753ms 2023-05-18T13:34:06.41327+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:06.42081+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.434136ms 2023-05-18T13:34:06.42086+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:11.41326+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=20.103656ms 2023-05-18T13:34:11.41332+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:11.41511+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.186868ms 2023-05-18T13:34:11.41516+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:16.40181+08:00 ERROR [539043,cab05376394f8332] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:34:16.40212+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.145717ms 2023-05-18T13:34:16.4022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:16.40864+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.057603ms 2023-05-18T13:34:16.40869+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:21.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.216605ms 2023-05-18T13:34:21.41073+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:21.4108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.890416ms 2023-05-18T13:34:21.41083+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:26.4057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.577048ms 2023-05-18T13:34:26.40577+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:26.41401+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.210005ms 2023-05-18T13:34:26.41406+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:31.40226+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.100216ms 2023-05-18T13:34:31.40232+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:31.40808+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.288906ms 2023-05-18T13:34:31.40814+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:36.40996+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.959001ms 2023-05-18T13:34:36.41003+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:36.41012+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.842315ms 2023-05-18T13:34:36.41015+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:41.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.758899ms 2023-05-18T13:34:41.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:41.41087+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.010217ms 2023-05-18T13:34:41.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:46.41667+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.765912ms 2023-05-18T13:34:46.41674+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:46.42485+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.041203ms 2023-05-18T13:34:46.42491+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:46.46161+08:00 ERROR [539043,692adaac041e8eae] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:34:51.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.228105ms 2023-05-18T13:34:51.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:51.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.066718ms 2023-05-18T13:34:51.41075+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:56.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.716398ms 2023-05-18T13:34:56.41086+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:34:56.41093+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.471523ms 2023-05-18T13:34:56.41097+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:01.41093+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.134804ms 2023-05-18T13:35:01.41099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:01.41109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.138018ms 2023-05-18T13:35:01.41112+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:06.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.932201ms 2023-05-18T13:35:06.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:06.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.23992ms 2023-05-18T13:35:06.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:11.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.924501ms 2023-05-18T13:35:11.41041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:11.41048+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.971316ms 2023-05-18T13:35:11.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:16.40256+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.910813ms 2023-05-18T13:35:16.40263+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:16.41097+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.292406ms 2023-05-18T13:35:16.41101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:16.4117+08:00 ERROR [539043,e909a695859fd3f9] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:35:21.40215+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.032415ms 2023-05-18T13:35:21.40223+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:21.40848+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.658111ms 2023-05-18T13:35:21.40854+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:26.41013+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.998302ms 2023-05-18T13:35:26.41021+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:26.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.000817ms 2023-05-18T13:35:26.41036+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:31.40571+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.204955ms 2023-05-18T13:35:31.4058+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:31.41088+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.237205ms 2023-05-18T13:35:31.41094+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:36.41006+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.921801ms 2023-05-18T13:35:36.41013+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:36.4102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.825415ms 2023-05-18T13:35:36.41023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:41.41098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.8287ms 2023-05-18T13:35:41.41105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:41.41114+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.719114ms 2023-05-18T13:35:41.41117+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:46.41627+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.973402ms 2023-05-18T13:35:46.41633+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:46.41648+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.511849ms 2023-05-18T13:35:46.41653+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:46.45266+08:00 ERROR [539043,be24bf72d8f44b76] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:35:51.40997+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.840615ms 2023-05-18T13:35:51.41003+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:51.41012+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.201505ms 2023-05-18T13:35:51.41017+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:56.4116+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.205717ms 2023-05-18T13:35:56.41166+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:35:56.41174+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.220232ms 2023-05-18T13:35:56.41179+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:01.40583+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.843964ms 2023-05-18T13:36:01.4059+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:01.40922+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.610497ms 2023-05-18T13:36:01.40927+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:06.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.280105ms 2023-05-18T13:36:06.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:06.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.219419ms 2023-05-18T13:36:06.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:11.4026+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.836812ms 2023-05-18T13:36:11.40266+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:11.41114+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.440408ms 2023-05-18T13:36:11.41124+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:16.40239+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.39752ms 2023-05-18T13:36:16.40245+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:16.41097+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.437307ms 2023-05-18T13:36:16.41102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:16.41174+08:00 ERROR [539043,0ea18b4de79619e8] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:36:21.41321+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=20.114957ms 2023-05-18T13:36:21.41328+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:21.41467+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.405758ms 2023-05-18T13:36:21.41473+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:26.4109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.63161ms 2023-05-18T13:36:26.41097+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:26.41104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.928429ms 2023-05-18T13:36:26.41107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:31.41051+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.215704ms 2023-05-18T13:36:31.4106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:31.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.130619ms 2023-05-18T13:36:31.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:36.41014+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.718199ms 2023-05-18T13:36:36.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:36.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.853515ms 2023-05-18T13:36:36.41033+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:41.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.287005ms 2023-05-18T13:36:41.41075+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:41.41085+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.965217ms 2023-05-18T13:36:41.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:46.40604+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.44142ms 2023-05-18T13:36:46.40612+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:46.415+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.832013ms 2023-05-18T13:36:46.41505+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:46.45349+08:00 ERROR [539043,88941507675fb042] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:36:51.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.157804ms 2023-05-18T13:36:51.41081+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:51.41088+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.117418ms 2023-05-18T13:36:51.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:56.40525+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.440046ms 2023-05-18T13:36:56.40531+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:36:56.41036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.8188ms 2023-05-18T13:36:56.41043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:01.41014+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.279605ms 2023-05-18T13:37:01.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:01.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.151519ms 2023-05-18T13:37:01.41034+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:06.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.423808ms 2023-05-18T13:37:06.41048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:06.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.27222ms 2023-05-18T13:37:06.41063+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:11.41008+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.230707ms 2023-05-18T13:37:11.41014+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:11.41047+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.8281ms 2023-05-18T13:37:11.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:16.40386+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.362832ms 2023-05-18T13:37:16.40393+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:16.41229+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.304506ms 2023-05-18T13:37:16.41233+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:16.41301+08:00 ERROR [539043,0f7560449855be7c] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:37:21.41062+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.288406ms 2023-05-18T13:37:21.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:21.41133+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.583424ms 2023-05-18T13:37:21.41137+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:26.40312+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.126029ms 2023-05-18T13:37:26.40319+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:26.40964+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.118504ms 2023-05-18T13:37:26.40969+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:31.40994+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.276206ms 2023-05-18T13:37:31.41001+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:31.41009+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.127119ms 2023-05-18T13:37:31.41012+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:36.40232+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.503108ms 2023-05-18T13:37:36.40239+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:36.40866+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.102703ms 2023-05-18T13:37:36.4087+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:41.41005+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.371109ms 2023-05-18T13:37:41.41011+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:41.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.8415ms 2023-05-18T13:37:41.41021+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:46.43336+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.447737ms 2023-05-18T13:37:46.43343+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:46.43348+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=27.063745ms 2023-05-18T13:37:46.43352+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:46.43362+08:00 ERROR [539043,d20370900c214eb8] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:37:51.41059+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.301506ms 2023-05-18T13:37:51.41066+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:51.41075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.507023ms 2023-05-18T13:37:51.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:56.41038+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.404607ms 2023-05-18T13:37:56.41045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:37:56.41054+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.093318ms 2023-05-18T13:37:56.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:01.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.322006ms 2023-05-18T13:38:01.41097+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:01.41108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.300721ms 2023-05-18T13:38:01.41113+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:06.40182+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.854213ms 2023-05-18T13:38:06.40188+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:06.40951+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.895214ms 2023-05-18T13:38:06.40956+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:11.40491+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.285044ms 2023-05-18T13:38:11.40497+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:11.41087+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.238705ms 2023-05-18T13:38:11.41092+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:16.40292+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.022815ms 2023-05-18T13:38:16.40299+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:16.41132+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.297806ms 2023-05-18T13:38:16.41137+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:16.41202+08:00 ERROR [539043,97a899db6ff8d37b] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:38:21.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.147404ms 2023-05-18T13:38:21.41041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:21.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.906316ms 2023-05-18T13:38:21.41054+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:26.40525+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.454447ms 2023-05-18T13:38:26.40531+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:26.41114+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.295306ms 2023-05-18T13:38:26.41119+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:31.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.946002ms 2023-05-18T13:38:31.41051+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:31.41061+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.21822ms 2023-05-18T13:38:31.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:36.40234+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.004114ms 2023-05-18T13:38:36.4024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:36.408+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.975602ms 2023-05-18T13:38:36.40804+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:41.41018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.827914ms 2023-05-18T13:38:41.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:41.41029+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.195805ms 2023-05-18T13:38:41.41031+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:46.42477+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.135203ms 2023-05-18T13:38:46.42483+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:46.42503+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.628625ms 2023-05-18T13:38:46.42507+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:46.45259+08:00 ERROR [539043,09e9100b38206d7e] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:38:51.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.10161ms 2023-05-18T13:38:51.41034+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:51.41041+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.869521ms 2023-05-18T13:38:51.41044+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:56.41075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.258111ms 2023-05-18T13:38:56.41083+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:38:56.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.378134ms 2023-05-18T13:38:56.41094+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:01.41084+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.218211ms 2023-05-18T13:39:01.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:01.41099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.326934ms 2023-05-18T13:39:01.41102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:06.41024+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.009308ms 2023-05-18T13:39:06.4103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:06.41037+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.629425ms 2023-05-18T13:39:06.41041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:11.41065+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.043609ms 2023-05-18T13:39:11.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:11.4108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.106031ms 2023-05-18T13:39:11.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:16.4025+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.183624ms 2023-05-18T13:39:16.40256+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:16.41055+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.936607ms 2023-05-18T13:39:16.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:16.41131+08:00 ERROR [539043,52fdcc5fe165c4a0] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:39:21.40854+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.305806ms 2023-05-18T13:39:21.40862+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:21.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.173911ms 2023-05-18T13:39:21.41054+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:26.40978+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.734604ms 2023-05-18T13:39:26.40986+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:26.40993+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.726826ms 2023-05-18T13:39:26.40996+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:31.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.058309ms 2023-05-18T13:39:31.41052+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:31.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.158931ms 2023-05-18T13:39:31.41068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:36.4108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.983808ms 2023-05-18T13:39:36.41086+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:36.41095+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.250833ms 2023-05-18T13:39:36.41098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:41.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.716504ms 2023-05-18T13:39:41.41033+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:41.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.698125ms 2023-05-18T13:39:41.41043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:46.40227+08:00 ERROR [539043,07bfbd6876959920] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:39:46.40638+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.104377ms 2023-05-18T13:39:46.40644+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:46.43185+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=31.12532ms 2023-05-18T13:39:46.43192+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:51.41+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.688604ms 2023-05-18T13:39:51.41007+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:51.41014+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.595324ms 2023-05-18T13:39:51.41017+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:56.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.330812ms 2023-05-18T13:39:56.41076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:39:56.41084+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.944629ms 2023-05-18T13:39:56.41087+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:01.41278+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.581229ms 2023-05-18T13:40:01.41285+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:01.41295+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.159459ms 2023-05-18T13:40:01.41299+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:06.40237+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.774819ms 2023-05-18T13:40:06.40243+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:06.40806+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.045609ms 2023-05-18T13:40:06.40812+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:11.40772+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.411094ms 2023-05-18T13:40:11.40778+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:11.40973+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.932707ms 2023-05-18T13:40:11.40977+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:16.40206+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.87432ms 2023-05-18T13:40:16.40212+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:16.40999+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.807006ms 2023-05-18T13:40:16.41005+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:16.41267+08:00 ERROR [539043,aacfc17e0c5ec66a] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:40:16.50216+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields:, module=monitor.ob, duration="39.5µs" 2023-05-18T13:40:16.50224+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields: module=monitor.ob, eventType=add, duration="5.801µs" 2023-05-18T13:40:16.50228+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields:, module=monitor.ob, duration="6.6µs" 2023-05-18T13:40:16.50232+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields:, module=monitor.ob, eventType=add, duration="4.7µs" 2023-05-18T13:40:16.50235+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T13:40:16.50971+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc00066e8c0 0xc00066e960 0xc00066ea00 0xc00066eaa0 0xc00066eb40 0xc00066ebe0 0xc00066ec80 0xc00066ed20 0xc00066edc0 0xc00066ee60 0xc00066ef00 0xc00066efa0 0xc00066f040 0xc00066f0e0 0xc00066f180 0xc00066f220 0xc00066f2c0 0xc00066f360 0xc00066f400 0xc00066f4a0 0xc00066f540 0xc00066f5e0 0xc00066f680 0xc00066f720 0xc00066f7c0 0xc00066f860 0xc00066f900 0xc00066f9a0 0xc00066fa40 0xc00066fae0 0xc00066fb80] CollectInterval:1s TimeAlign:false} 2023-05-18T13:40:16.51195+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T13:40:16.51198+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields: input=mysqlTableInput, duration="4.2µs" 2023-05-18T13:40:16.512+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields:, input=mysqlTableInput, duration="22.8µs" 2023-05-18T13:40:16.51202+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields: eventType=add, module=monitor.ob, duration=9.703931ms, error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:40:16.51204+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields:, module=monitor.ob, eventType=add, duration=9.721831ms 2023-05-18T13:40:16.51206+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields:, module=monitor.ob, duration=9.783232ms 2023-05-18T13:40:16.51207+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields: duration=9.837833ms, module=monitor.ob, eventType=add 2023-05-18T13:40:16.51208+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields: duration=9.960834ms, module=monitor.ob 2023-05-18T13:40:16.51213+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 19 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T13:40:21.41055+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.588824ms 2023-05-18T13:40:21.41063+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:21.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.072609ms 2023-05-18T13:40:21.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:26.41112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.045622ms 2023-05-18T13:40:26.41118+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:26.41127+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.110744ms 2023-05-18T13:40:26.41131+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:31.40998+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.057409ms 2023-05-18T13:40:31.41004+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:31.41012+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.817227ms 2023-05-18T13:40:31.41014+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:36.40596+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.484955ms 2023-05-18T13:40:36.40602+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:36.41416+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.092909ms 2023-05-18T13:40:36.4142+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:41.40588+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.381467ms 2023-05-18T13:40:41.40594+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:41.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.379614ms 2023-05-18T13:40:41.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:46.40773+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.129823ms 2023-05-18T13:40:46.40783+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:46.4165+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.624916ms 2023-05-18T13:40:46.41655+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:46.43989+08:00 ERROR [539043,6560a8183fc52d6a] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:40:51.40466+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.312353ms 2023-05-18T13:40:51.40474+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:51.41047+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.14451ms 2023-05-18T13:40:51.41052+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:56.4028+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.83422ms 2023-05-18T13:40:56.40287+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:40:56.40795+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.365713ms 2023-05-18T13:40:56.408+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:01.40272+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.993622ms 2023-05-18T13:41:01.4028+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:01.41113+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.283412ms 2023-05-18T13:41:01.41118+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:06.40586+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.128864ms 2023-05-18T13:41:06.40594+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:06.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.042709ms 2023-05-18T13:41:06.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:11.40937+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.696511ms 2023-05-18T13:41:11.40944+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:11.41012+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.983207ms 2023-05-18T13:41:11.41018+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:16.40278+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.293825ms 2023-05-18T13:41:16.40287+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:16.41062+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.705504ms 2023-05-18T13:41:16.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:16.41144+08:00 ERROR [539043,f3ff0f65d20541d5] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:41:21.41018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.629503ms 2023-05-18T13:41:21.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:21.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.595124ms 2023-05-18T13:41:21.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:26.40287+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.88382ms 2023-05-18T13:41:26.40294+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:26.41146+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.466115ms 2023-05-18T13:41:26.41153+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:31.41078+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.981029ms 2023-05-18T13:41:31.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:31.41126+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.656117ms 2023-05-18T13:41:31.4113+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:36.41006+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.09071ms 2023-05-18T13:41:36.41014+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:36.41022+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.913429ms 2023-05-18T13:41:36.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:41.41038+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.879306ms 2023-05-18T13:41:41.41045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:41.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.003129ms 2023-05-18T13:41:41.41059+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:46.4209+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.661303ms 2023-05-18T13:41:46.42097+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:46.42101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.341634ms 2023-05-18T13:41:46.42104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:46.45709+08:00 ERROR [539043,38461e27822b1054] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:41:51.40929+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.281006ms 2023-05-18T13:41:51.40935+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:51.41148+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.603116ms 2023-05-18T13:41:51.41154+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:56.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.984008ms 2023-05-18T13:41:56.41052+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:41:56.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.081331ms 2023-05-18T13:41:56.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:01.41019+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.666903ms 2023-05-18T13:42:01.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:01.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.486822ms 2023-05-18T13:42:01.41036+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:06.41084+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.270712ms 2023-05-18T13:42:06.4109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:06.41099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.115931ms 2023-05-18T13:42:06.41103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:11.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.206711ms 2023-05-18T13:42:11.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:11.41088+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.00953ms 2023-05-18T13:42:11.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:16.40286+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.165423ms 2023-05-18T13:42:16.40293+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:16.41099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.025608ms 2023-05-18T13:42:16.41104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:16.41171+08:00 ERROR [539043,b64a43412ced0067] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:42:21.41323+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.458062ms 2023-05-18T13:42:21.4133+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:21.41353+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.073909ms 2023-05-18T13:42:21.41357+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:26.41131+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.220311ms 2023-05-18T13:42:26.41137+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:26.41146+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.092944ms 2023-05-18T13:42:26.41149+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:31.40756+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=14.439795ms 2023-05-18T13:42:31.40764+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:31.40975+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.900406ms 2023-05-18T13:42:31.4098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:36.41092+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.275912ms 2023-05-18T13:42:36.41099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:36.41107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.341634ms 2023-05-18T13:42:36.4111+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:41.41124+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.678918ms 2023-05-18T13:42:41.41135+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:41.41143+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.976743ms 2023-05-18T13:42:41.41146+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:46.41635+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.793618ms 2023-05-18T13:42:46.41643+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:46.4243+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.804706ms 2023-05-18T13:42:46.42435+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:46.46708+08:00 ERROR [539043,3b3896420610701d] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:42:51.40947+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.571403ms 2023-05-18T13:42:51.40953+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:51.40964+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.399221ms 2023-05-18T13:42:51.4097+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:56.41132+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.780819ms 2023-05-18T13:42:56.41141+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:42:56.41155+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.928942ms 2023-05-18T13:42:56.4116+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:01.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.826319ms 2023-05-18T13:43:01.41086+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:01.41093+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.633738ms 2023-05-18T13:43:01.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:06.40884+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.441408ms 2023-05-18T13:43:06.4089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:06.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.067509ms 2023-05-18T13:43:06.41066+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:11.40205+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.358212ms 2023-05-18T13:43:11.40211+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:11.40875+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.221811ms 2023-05-18T13:43:11.4088+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:16.40306+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.080222ms 2023-05-18T13:43:16.40312+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:16.41103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.856806ms 2023-05-18T13:43:16.41108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:16.41181+08:00 ERROR [539043,325fc346bd148103] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:43:21.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.683003ms 2023-05-18T13:43:21.41065+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:21.41074+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.773027ms 2023-05-18T13:43:21.41077+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:26.41071+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.222111ms 2023-05-18T13:43:26.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:26.41146+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.690338ms 2023-05-18T13:43:26.41151+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:31.41003+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.254611ms 2023-05-18T13:43:31.41011+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:31.41018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.992729ms 2023-05-18T13:43:31.41021+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:36.40314+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.231424ms 2023-05-18T13:43:36.4032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:36.40896+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.346213ms 2023-05-18T13:43:36.40902+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:41.41065+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.160611ms 2023-05-18T13:43:41.41073+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:41.41082+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.805527ms 2023-05-18T13:43:41.41086+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:46.4158+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.573316ms 2023-05-18T13:43:46.41587+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:46.42541+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.468128ms 2023-05-18T13:43:46.42547+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:46.45631+08:00 ERROR [539043,c4748d018fba2b99] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:43:51.41111+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.594916ms 2023-05-18T13:43:51.41117+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:51.41124+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.287133ms 2023-05-18T13:43:51.41127+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:56.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.991808ms 2023-05-18T13:43:56.4106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:43:56.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.897328ms 2023-05-18T13:43:56.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:01.41009+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.681604ms 2023-05-18T13:44:01.41015+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:01.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.722426ms 2023-05-18T13:44:01.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:06.40749+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=14.218492ms 2023-05-18T13:44:06.40755+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:06.41022+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.14671ms 2023-05-18T13:44:06.41027+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:11.41016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.591703ms 2023-05-18T13:44:11.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:11.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.493322ms 2023-05-18T13:44:11.41036+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:16.40277+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.315126ms 2023-05-18T13:44:16.40283+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:16.41074+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.877007ms 2023-05-18T13:44:16.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:16.41147+08:00 ERROR [539043,61f1633e9cf0e1e2] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:44:21.4014+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.441014ms 2023-05-18T13:44:21.40148+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:21.40867+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.13871ms 2023-05-18T13:44:21.40872+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:26.41064+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.036708ms 2023-05-18T13:44:26.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:26.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.02733ms 2023-05-18T13:44:26.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:31.40313+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.138037ms 2023-05-18T13:44:31.40319+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:31.40995+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.199711ms 2023-05-18T13:44:31.40999+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:36.40986+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.865106ms 2023-05-18T13:44:36.40992+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:36.41+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.823927ms 2023-05-18T13:44:36.41003+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:41.40751+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=14.360294ms 2023-05-18T13:44:41.4076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:41.40997+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.13481ms 2023-05-18T13:44:41.41002+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:46.40721+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.89282ms 2023-05-18T13:44:46.40727+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:46.4152+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.897707ms 2023-05-18T13:44:46.41525+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:46.44807+08:00 ERROR [539043,32579d70ddce2377] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:44:51.41322+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.603164ms 2023-05-18T13:44:51.41328+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:51.41422+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.027609ms 2023-05-18T13:44:51.41427+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:56.40231+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.778619ms 2023-05-18T13:44:56.40237+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:44:56.40836+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.180011ms 2023-05-18T13:44:56.40841+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:01.40267+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.86772ms 2023-05-18T13:45:01.40273+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:01.40865+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.09091ms 2023-05-18T13:45:01.4087+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:06.40311+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.111037ms 2023-05-18T13:45:06.40317+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:06.40985+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.940307ms 2023-05-18T13:45:06.40991+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:11.41016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.11531ms 2023-05-18T13:45:11.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:11.41029+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.02323ms 2023-05-18T13:45:11.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:16.40222+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.992422ms 2023-05-18T13:45:16.40234+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:16.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.989907ms 2023-05-18T13:45:16.41048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:16.41113+08:00 ERROR [539043,2eff304e4573406c] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:45:21.40981+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.960907ms 2023-05-18T13:45:21.4099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:21.40997+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.660125ms 2023-05-18T13:45:21.41+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:26.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.14011ms 2023-05-18T13:45:26.41052+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:26.41062+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.183932ms 2023-05-18T13:45:26.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:31.4101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.009708ms 2023-05-18T13:45:31.41017+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:31.41026+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.07973ms 2023-05-18T13:45:31.41029+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:36.41108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.17841ms 2023-05-18T13:45:36.41115+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:36.41123+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.189232ms 2023-05-18T13:45:36.41127+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:41.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.965707ms 2023-05-18T13:45:41.4104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:41.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.843627ms 2023-05-18T13:45:41.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:46.4162+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.89112ms 2023-05-18T13:45:46.41627+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:46.42436+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.965307ms 2023-05-18T13:45:46.42442+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:46.45427+08:00 ERROR [539043,71b96f455c2e4afa] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:45:46.48104+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 1609388 fields:, error="open /proc/1609388/status: no such file or directory" 2023-05-18T13:45:46.4811+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 1609405 fields:, error="open /proc/1609405/status: no such file or directory" 2023-05-18T13:45:51.41229+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.801733ms 2023-05-18T13:45:51.41237+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:51.41245+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.781254ms 2023-05-18T13:45:51.41248+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:56.41016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.914007ms 2023-05-18T13:45:56.41023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:45:56.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.745726ms 2023-05-18T13:45:56.41036+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:01.4102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.134209ms 2023-05-18T13:46:01.41027+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:01.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.159831ms 2023-05-18T13:46:01.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:06.4128+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.289938ms 2023-05-18T13:46:06.41288+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:06.41297+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.047957ms 2023-05-18T13:46:06.41301+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:11.40482+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.974848ms 2023-05-18T13:46:11.40488+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:11.41244+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.493515ms 2023-05-18T13:46:11.4125+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:16.40243+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.82952ms 2023-05-18T13:46:16.4025+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:16.41066+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.000508ms 2023-05-18T13:46:16.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:16.41139+08:00 ERROR [539043,689e3bda67440aaf] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:46:21.40721+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.383981ms 2023-05-18T13:46:21.40727+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:21.41176+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.235911ms 2023-05-18T13:46:21.41182+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:26.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.997907ms 2023-05-18T13:46:26.41029+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:26.41036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.993229ms 2023-05-18T13:46:26.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:31.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.055709ms 2023-05-18T13:46:31.41073+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:31.4108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.03463ms 2023-05-18T13:46:31.41083+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:36.41102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.253511ms 2023-05-18T13:46:36.41109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:36.41116+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.453735ms 2023-05-18T13:46:36.41119+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:41.41062+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.14681ms 2023-05-18T13:46:41.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:41.41076+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.258133ms 2023-05-18T13:46:41.41081+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:46.42254+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.602324ms 2023-05-18T13:46:46.42262+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:46.42269+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.173118ms 2023-05-18T13:46:46.42272+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:46.45488+08:00 ERROR [539043,19ad2461f9c5b102] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:46:46.46412+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 1616214 fields:, error="open /proc/1616214/status: no such file or directory" 2023-05-18T13:46:46.46417+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 1616235 fields: error="open /proc/1616235/status: no such file or directory" 2023-05-18T13:46:51.41171+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.798741ms 2023-05-18T13:46:51.4118+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:51.41187+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.968821ms 2023-05-18T13:46:51.4119+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:56.41096+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.14101ms 2023-05-18T13:46:56.41102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:46:56.41109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.403235ms 2023-05-18T13:46:56.41112+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:01.41076+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.191111ms 2023-05-18T13:47:01.41082+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:01.4109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.279433ms 2023-05-18T13:47:01.41093+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:06.41114+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.286512ms 2023-05-18T13:47:06.41122+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:06.4113+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.270233ms 2023-05-18T13:47:06.41133+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:11.41009+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.899907ms 2023-05-18T13:47:11.41017+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:11.41026+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.706325ms 2023-05-18T13:47:11.4103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:16.40236+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.290325ms 2023-05-18T13:47:16.40242+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:16.41088+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.414913ms 2023-05-18T13:47:16.41093+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:16.41167+08:00 ERROR [539043,0c06bfde9c3d3ae2] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:47:21.40397+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.507542ms 2023-05-18T13:47:21.40403+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:21.41055+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.13451ms 2023-05-18T13:47:21.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:26.41129+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.338934ms 2023-05-18T13:47:26.41135+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:26.41222+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.106309ms 2023-05-18T13:47:26.41227+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:31.40495+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.923047ms 2023-05-18T13:47:31.40502+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:31.41128+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.321013ms 2023-05-18T13:47:31.41132+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:36.41011+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.200911ms 2023-05-18T13:47:36.41018+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:36.41025+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.161332ms 2023-05-18T13:47:36.41028+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:41.4031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.142736ms 2023-05-18T13:47:41.40317+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:41.40994+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.046809ms 2023-05-18T13:47:41.40998+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:46.41555+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.993522ms 2023-05-18T13:47:46.41567+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:46.42366+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.872106ms 2023-05-18T13:47:46.4237+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:46.4568+08:00 ERROR [539043,340836df716ee6ee] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:47:51.41066+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.244211ms 2023-05-18T13:47:51.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:51.41078+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.372134ms 2023-05-18T13:47:51.41081+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:56.40961+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.051816ms 2023-05-18T13:47:56.40967+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:47:56.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.404513ms 2023-05-18T13:47:56.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:01.41328+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.685466ms 2023-05-18T13:48:01.41334+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:01.41524+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.503115ms 2023-05-18T13:48:01.41531+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:06.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.807305ms 2023-05-18T13:48:06.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:06.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.868828ms 2023-05-18T13:48:06.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:11.40203+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.929521ms 2023-05-18T13:48:11.40209+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:11.40793+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.14631ms 2023-05-18T13:48:11.40798+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:16.40255+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.057822ms 2023-05-18T13:48:16.40263+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:16.41082+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.16171ms 2023-05-18T13:48:16.41088+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:16.41155+08:00 ERROR [539043,e3c4dd4ad19dcde4] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:48:21.40407+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.570942ms 2023-05-18T13:48:21.40414+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:21.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.061309ms 2023-05-18T13:48:21.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:26.4099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.031108ms 2023-05-18T13:48:26.40998+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:26.41007+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.944028ms 2023-05-18T13:48:26.4101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:31.40271+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.740818ms 2023-05-18T13:48:31.40278+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:31.40864+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.081809ms 2023-05-18T13:48:31.40869+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:36.40779+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.777586ms 2023-05-18T13:48:36.40785+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:36.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.901306ms 2023-05-18T13:48:36.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:41.4054+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.525255ms 2023-05-18T13:48:41.40547+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:41.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.625503ms 2023-05-18T13:48:41.41048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:46.41055+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.815219ms 2023-05-18T13:48:46.41063+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:46.41867+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.959307ms 2023-05-18T13:48:46.41871+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:46.44673+08:00 ERROR [539043,732050552903e94d] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:48:51.40945+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.676204ms 2023-05-18T13:48:51.40951+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:51.40962+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.485822ms 2023-05-18T13:48:51.40966+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:56.40222+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.207624ms 2023-05-18T13:48:56.4023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:48:56.40813+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.446914ms 2023-05-18T13:48:56.40819+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:01.41041+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.916107ms 2023-05-18T13:49:01.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:01.41055+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.586924ms 2023-05-18T13:49:01.4106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:06.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.107309ms 2023-05-18T13:49:06.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:06.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.119731ms 2023-05-18T13:49:06.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:11.41108+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.13951ms 2023-05-18T13:49:11.41114+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:11.41122+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.381335ms 2023-05-18T13:49:11.41125+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:16.40177+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.516315ms 2023-05-18T13:49:16.40183+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:16.40974+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.860606ms 2023-05-18T13:49:16.40979+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:16.41048+08:00 ERROR [539043,cb2f6aed457118c5] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:49:21.40165+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.690417ms 2023-05-18T13:49:21.40171+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:21.40781+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.11681ms 2023-05-18T13:49:21.40787+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:26.40549+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.096764ms 2023-05-18T13:49:26.40555+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:26.4138+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.190611ms 2023-05-18T13:49:26.41387+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:31.40694+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.591883ms 2023-05-18T13:49:31.40701+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:31.41007+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.979007ms 2023-05-18T13:49:31.41011+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:36.40242+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.695917ms 2023-05-18T13:49:36.4025+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:36.40864+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.226411ms 2023-05-18T13:49:36.40869+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:41.40195+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.634017ms 2023-05-18T13:49:41.40201+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:41.40969+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.644903ms 2023-05-18T13:49:41.40975+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:46.42446+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.955708ms 2023-05-18T13:49:46.42452+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:46.42467+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.831627ms 2023-05-18T13:49:46.42471+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:46.44807+08:00 ERROR [539043,b0642b320f583fe1] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:49:51.40225+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.87862ms 2023-05-18T13:49:51.40231+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:51.40789+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.870506ms 2023-05-18T13:49:51.40795+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:56.41134+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.291912ms 2023-05-18T13:49:56.41141+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:49:56.41148+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.651238ms 2023-05-18T13:49:56.41151+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:01.4113+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.098823ms 2023-05-18T13:50:01.41137+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:01.41146+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.866941ms 2023-05-18T13:50:01.41149+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:06.40973+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.761905ms 2023-05-18T13:50:06.40979+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:06.40988+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.579124ms 2023-05-18T13:50:06.40991+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:11.41117+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.401813ms 2023-05-18T13:50:11.41123+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:11.41133+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.607037ms 2023-05-18T13:50:11.41136+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:16.40236+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.95842ms 2023-05-18T13:50:16.40243+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:16.41095+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.473214ms 2023-05-18T13:50:16.411+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:16.41226+08:00 ERROR [539043,e3b5ad827c20a845] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:50:16.51265+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields: module=monitor.ob, duration="24.201µs" 2023-05-18T13:50:16.51272+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields: eventType=add, duration="7.8µs", module=monitor.ob 2023-05-18T13:50:16.51275+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields:, module=monitor.ob, duration="4.9µs" 2023-05-18T13:50:16.51279+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields: eventType=add, duration="4.601µs", module=monitor.ob 2023-05-18T13:50:16.51282+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T13:50:16.51677+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc000384640 0xc0003846e0 0xc000384780 0xc000384820 0xc0003848c0 0xc000384960 0xc000384a00 0xc000384aa0 0xc000384b40 0xc000384be0 0xc000384c80 0xc000384d20 0xc000384dc0 0xc000384e60 0xc000384f00 0xc000384fa0 0xc000385040 0xc0003850e0 0xc000385180 0xc000385220 0xc0003852c0 0xc000385360 0xc000385400 0xc0003854a0 0xc000385540 0xc0003855e0 0xc000385680 0xc000385720 0xc0003857c0 0xc000385860 0xc000385900] CollectInterval:1s TimeAlign:false} 2023-05-18T13:50:16.51757+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T13:50:16.51761+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields: duration="6.7µs", input=mysqlTableInput 2023-05-18T13:50:16.51763+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields:, input=mysqlTableInput, duration="25.7µs" 2023-05-18T13:50:16.51765+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields:, module=monitor.ob, eventType=add, error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)", duration=4.868166ms 2023-05-18T13:50:16.51767+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields: duration=4.886466ms, module=monitor.ob, eventType=add 2023-05-18T13:50:16.5177+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields: module=monitor.ob, duration=4.955267ms 2023-05-18T13:50:16.51772+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields:, eventType=add, module=monitor.ob, duration=5.001267ms 2023-05-18T13:50:16.51773+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields:, module=monitor.ob, duration=5.102169ms 2023-05-18T13:50:16.51775+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 20 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T13:50:21.41012+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.828906ms 2023-05-18T13:50:21.4102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:21.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.923828ms 2023-05-18T13:50:21.4103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:26.41064+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.451114ms 2023-05-18T13:50:26.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:26.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.370534ms 2023-05-18T13:50:26.41083+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:31.41081+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.17171ms 2023-05-18T13:50:31.41087+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:31.41096+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.251832ms 2023-05-18T13:50:31.41101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:36.40616+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.198465ms 2023-05-18T13:50:36.40622+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:36.41427+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.004208ms 2023-05-18T13:50:36.41431+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:41.41036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.693604ms 2023-05-18T13:50:41.41044+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:41.41051+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.879927ms 2023-05-18T13:50:41.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:46.43508+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=27.642973ms 2023-05-18T13:50:46.43514+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:46.43525+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=27.258868ms 2023-05-18T13:50:46.43528+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:46.45591+08:00 ERROR [539043,b97b78c2f4d9607a] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:50:51.41123+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.343913ms 2023-05-18T13:50:51.41129+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:51.41139+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.365334ms 2023-05-18T13:50:51.41143+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:56.40594+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.408554ms 2023-05-18T13:50:56.406+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:50:56.41381+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.759105ms 2023-05-18T13:50:56.41387+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:01.40344+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.159237ms 2023-05-18T13:51:01.40352+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:01.41009+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.697504ms 2023-05-18T13:51:01.41015+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:06.40933+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.560002ms 2023-05-18T13:51:06.4094+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:06.40947+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.457522ms 2023-05-18T13:51:06.4095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:11.41024+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.629203ms 2023-05-18T13:51:11.41031+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:11.41039+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.629825ms 2023-05-18T13:51:11.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:16.40298+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.135524ms 2023-05-18T13:51:16.40304+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:16.4113+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.216611ms 2023-05-18T13:51:16.41135+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:16.41214+08:00 ERROR [539043,6d6fb439b1a0ae09] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:51:21.41039+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.018109ms 2023-05-18T13:51:21.41068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:21.41119+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.655738ms 2023-05-18T13:51:21.41123+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:26.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.249811ms 2023-05-18T13:51:26.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:26.41066+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.137631ms 2023-05-18T13:51:26.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:31.40774+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=14.032889ms 2023-05-18T13:51:31.40781+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:31.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.983408ms 2023-05-18T13:51:31.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:36.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.052308ms 2023-05-18T13:51:36.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:36.41066+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.983829ms 2023-05-18T13:51:36.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:41.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.914407ms 2023-05-18T13:51:41.4106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:41.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.979629ms 2023-05-18T13:51:41.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:46.44299+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=25.957451ms 2023-05-18T13:51:46.44305+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:46.44316+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=26.66896ms 2023-05-18T13:51:46.44318+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:46.46465+08:00 ERROR [539043,cf1261fb4f7a8593] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:51:51.41166+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.674417ms 2023-05-18T13:51:51.41176+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:51.41226+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.652752ms 2023-05-18T13:51:51.4123+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:56.40227+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.835719ms 2023-05-18T13:51:56.40235+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:51:56.40806+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.968207ms 2023-05-18T13:51:56.40811+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:01.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.368113ms 2023-05-18T13:52:01.41075+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:01.41083+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.182632ms 2023-05-18T13:52:01.41086+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:06.4122+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.697217ms 2023-05-18T13:52:06.41228+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:06.41235+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.401348ms 2023-05-18T13:52:06.41238+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:11.40985+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.621702ms 2023-05-18T13:52:11.40992+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:11.41004+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.476822ms 2023-05-18T13:52:11.41007+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:16.40243+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.761718ms 2023-05-18T13:52:16.40249+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:16.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.15151ms 2023-05-18T13:52:16.41073+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:16.41138+08:00 ERROR [539043,96f1b82ab0a643b6] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:52:21.40966+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.723404ms 2023-05-18T13:52:21.40973+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:21.40998+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.798527ms 2023-05-18T13:52:21.41003+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:26.40254+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.802319ms 2023-05-18T13:52:26.40263+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:26.40832+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.982808ms 2023-05-18T13:52:26.40839+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:31.41201+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.227011ms 2023-05-18T13:52:31.41207+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:31.41215+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.437148ms 2023-05-18T13:52:31.41218+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:36.40526+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.200451ms 2023-05-18T13:52:36.40532+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:36.41328+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.910907ms 2023-05-18T13:52:36.41333+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:41.40201+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.640717ms 2023-05-18T13:52:41.40208+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:41.40798+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.983608ms 2023-05-18T13:52:41.40804+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:46.41595+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.933921ms 2023-05-18T13:52:46.41602+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:46.42453+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.434213ms 2023-05-18T13:52:46.42457+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:46.45676+08:00 ERROR [539043,3204ae790eeaecb5] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:52:51.40861+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.436109ms 2023-05-18T13:52:51.40868+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:51.40995+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.11141ms 2023-05-18T13:52:51.41+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:56.40962+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.002616ms 2023-05-18T13:52:56.40968+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:52:56.40999+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.003608ms 2023-05-18T13:52:56.41003+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:01.411+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.547415ms 2023-05-18T13:53:01.41108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:01.41118+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.554737ms 2023-05-18T13:53:01.41121+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:06.41106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.221411ms 2023-05-18T13:53:06.41112+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:06.41119+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.279333ms 2023-05-18T13:53:06.41122+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:11.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.228911ms 2023-05-18T13:53:11.41053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:11.41062+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.168932ms 2023-05-18T13:53:11.41066+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:16.40244+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.90092ms 2023-05-18T13:53:16.40251+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:16.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.026808ms 2023-05-18T13:53:16.41063+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:16.41128+08:00 ERROR [539043,858c39fd1a378247] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:53:21.40634+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.497869ms 2023-05-18T13:53:21.4064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:21.41055+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.856106ms 2023-05-18T13:53:21.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:26.41084+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.470515ms 2023-05-18T13:53:26.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:26.411+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.233233ms 2023-05-18T13:53:26.41105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:31.40966+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.064809ms 2023-05-18T13:53:31.40973+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:31.4098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.662625ms 2023-05-18T13:53:31.40983+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:36.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.13521ms 2023-05-18T13:53:36.41079+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:36.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.313534ms 2023-05-18T13:53:36.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:41.40585+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.538355ms 2023-05-18T13:53:41.40592+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:41.41468+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.704417ms 2023-05-18T13:53:41.41473+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:46.40671+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.184024ms 2023-05-18T13:53:46.40677+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:46.41494+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.12621ms 2023-05-18T13:53:46.41498+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:46.45411+08:00 ERROR [539043,378a3a569112b427] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:53:51.41004+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.818206ms 2023-05-18T13:53:51.41011+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:51.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.725126ms 2023-05-18T13:53:51.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:56.40199+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.008921ms 2023-05-18T13:53:56.40208+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:53:56.40811+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.539015ms 2023-05-18T13:53:56.40816+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:01.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.250511ms 2023-05-18T13:54:01.41092+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:01.411+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.399835ms 2023-05-18T13:54:01.41103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:06.41084+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.473115ms 2023-05-18T13:54:06.4109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:06.41097+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.558537ms 2023-05-18T13:54:06.411+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:11.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.055409ms 2023-05-18T13:54:11.41092+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:11.41099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.05663ms 2023-05-18T13:54:11.41102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:16.40203+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.678517ms 2023-05-18T13:54:16.4021+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:16.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.144309ms 2023-05-18T13:54:16.41036+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:16.41109+08:00 ERROR [539043,b3e1c47dcaa24e1c] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:54:21.41018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.945829ms 2023-05-18T13:54:21.41027+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:21.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.264612ms 2023-05-18T13:54:21.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:26.41097+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.813519ms 2023-05-18T13:54:26.41104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:26.41112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.905841ms 2023-05-18T13:54:26.41115+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:31.40267+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.96222ms 2023-05-18T13:54:31.40274+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:31.40937+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.982721ms 2023-05-18T13:54:31.40942+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:36.41122+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.580316ms 2023-05-18T13:54:36.41129+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:36.41136+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.717439ms 2023-05-18T13:54:36.41139+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:41.40316+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.154437ms 2023-05-18T13:54:41.40325+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:41.40979+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.920806ms 2023-05-18T13:54:41.40984+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:46.41535+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.089417ms 2023-05-18T13:54:46.41541+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:46.41546+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.710712ms 2023-05-18T13:54:46.4155+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:46.47043+08:00 ERROR [539043,341f683d7e307bdf] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:54:51.4047+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.196151ms 2023-05-18T13:54:51.40477+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:51.41059+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.955507ms 2023-05-18T13:54:51.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:56.4109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.139209ms 2023-05-18T13:54:56.41097+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:54:56.41104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.596537ms 2023-05-18T13:54:56.41107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:01.4023+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.067522ms 2023-05-18T13:55:01.40236+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:01.40872+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.843819ms 2023-05-18T13:55:01.40878+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:06.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.814527ms 2023-05-18T13:55:06.41077+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:06.41084+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.245112ms 2023-05-18T13:55:06.41087+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:11.40996+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.025809ms 2023-05-18T13:55:11.41003+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:11.41011+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.874528ms 2023-05-18T13:55:11.41014+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:16.40256+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.230425ms 2023-05-18T13:55:16.40264+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:16.41201+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.319525ms 2023-05-18T13:55:16.41206+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:16.41278+08:00 ERROR [539043,3c48c296c2107acb] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:55:21.41037+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.365113ms 2023-05-18T13:55:21.41045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:21.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.318233ms 2023-05-18T13:55:21.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:26.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.259011ms 2023-05-18T13:55:26.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:26.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.300634ms 2023-05-18T13:55:26.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:31.40328+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.282126ms 2023-05-18T13:55:31.40336+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:31.40844+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.968107ms 2023-05-18T13:55:31.40848+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:36.41043+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.975808ms 2023-05-18T13:55:36.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:36.41059+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.821027ms 2023-05-18T13:55:36.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:41.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.553716ms 2023-05-18T13:55:41.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:41.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.425235ms 2023-05-18T13:55:41.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:46.41537+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.912321ms 2023-05-18T13:55:46.41544+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:46.4237+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.18831ms 2023-05-18T13:55:46.42375+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:46.45679+08:00 ERROR [539043,0939c2c9eb109f08] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:55:51.40317+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.523028ms 2023-05-18T13:55:51.40325+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:51.40888+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.558515ms 2023-05-18T13:55:51.40893+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:56.41074+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.668817ms 2023-05-18T13:55:56.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:55:56.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.634838ms 2023-05-18T13:55:56.41095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:01.40476+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.493048ms 2023-05-18T13:56:01.40483+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:01.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.370408ms 2023-05-18T13:56:01.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:06.40982+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.781801ms 2023-05-18T13:56:06.40988+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:06.40995+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.409012ms 2023-05-18T13:56:06.40999+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:11.41008+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.957402ms 2023-05-18T13:56:11.41015+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:11.41022+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.860418ms 2023-05-18T13:56:11.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:16.40211+08:00 ERROR [539043,6b58f5fddac137df] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:56:16.40224+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.669612ms 2023-05-18T13:56:16.40228+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:16.40842+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.48651ms 2023-05-18T13:56:16.40846+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:21.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.373709ms 2023-05-18T13:56:21.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:21.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.115621ms 2023-05-18T13:56:21.41052+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:26.41085+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.336208ms 2023-05-18T13:56:26.41115+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:26.41194+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.255536ms 2023-05-18T13:56:26.41199+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:31.408+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=14.119882ms 2023-05-18T13:56:31.40806+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:31.41066+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.053004ms 2023-05-18T13:56:31.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:36.40984+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.960003ms 2023-05-18T13:56:36.4099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:36.40998+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.606815ms 2023-05-18T13:56:36.41+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:41.41025+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.085604ms 2023-05-18T13:56:41.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:41.41039+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.973019ms 2023-05-18T13:56:41.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:46.4343+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=26.575243ms 2023-05-18T13:56:46.43436+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:46.43446+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.240739ms 2023-05-18T13:56:46.43449+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:46.45564+08:00 ERROR [539043,149ca8b7f0b07e1e] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:56:51.41098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.050204ms 2023-05-18T13:56:51.41105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:51.41113+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.188022ms 2023-05-18T13:56:51.41116+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:56.41122+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.297407ms 2023-05-18T13:56:56.41128+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:56:56.41136+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.646028ms 2023-05-18T13:56:56.4114+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:01.41025+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.222606ms 2023-05-18T13:57:01.41031+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:01.41039+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.201922ms 2023-05-18T13:57:01.41041+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:06.40311+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.129331ms 2023-05-18T13:57:06.40317+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:06.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.219106ms 2023-05-18T13:57:06.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:11.40282+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.130718ms 2023-05-18T13:57:11.40291+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:11.40848+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.107405ms 2023-05-18T13:57:11.40854+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:16.40227+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.164819ms 2023-05-18T13:57:16.40234+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:16.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.917803ms 2023-05-18T13:57:16.41036+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:16.41101+08:00 ERROR [539043,99af583796f86bb8] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:57:21.40354+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.174631ms 2023-05-18T13:57:21.40363+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:21.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.105805ms 2023-05-18T13:57:21.4106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:26.4112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.221923ms 2023-05-18T13:57:26.41126+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:26.41132+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.230306ms 2023-05-18T13:57:26.41136+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:31.40278+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.856515ms 2023-05-18T13:57:31.40286+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:31.4087+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.096604ms 2023-05-18T13:57:31.40875+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:36.4121+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.140334ms 2023-05-18T13:57:36.41216+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:36.41222+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.378408ms 2023-05-18T13:57:36.41225+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:41.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.919102ms 2023-05-18T13:57:41.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:41.41069+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.02732ms 2023-05-18T13:57:41.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:46.42305+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.206222ms 2023-05-18T13:57:46.42312+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:46.43762+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=15.576401ms 2023-05-18T13:57:46.43769+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:46.45411+08:00 ERROR [539043,13512e48c013925b] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:57:51.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.195806ms 2023-05-18T13:57:51.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:51.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.178921ms 2023-05-18T13:57:51.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:56.41084+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.635212ms 2023-05-18T13:57:56.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:57:56.41099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.585927ms 2023-05-18T13:57:56.41103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:01.40988+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.011203ms 2023-05-18T13:58:01.40994+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:01.41003+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.835917ms 2023-05-18T13:58:01.41007+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:06.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.010004ms 2023-05-18T13:58:06.41066+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:06.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.02292ms 2023-05-18T13:58:06.41076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:11.41266+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.706425ms 2023-05-18T13:58:11.41273+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:11.41279+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.298449ms 2023-05-18T13:58:11.41282+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:16.40308+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.189119ms 2023-05-18T13:58:16.40314+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:16.41121+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.031404ms 2023-05-18T13:58:16.41126+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:16.4119+08:00 ERROR [539043,c78166eeab4101bb] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:58:21.40232+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.996816ms 2023-05-18T13:58:21.40238+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:21.40794+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.948003ms 2023-05-18T13:58:21.408+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:26.40577+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.187258ms 2023-05-18T13:58:26.40583+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:26.41018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.891702ms 2023-05-18T13:58:26.41023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:31.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.049004ms 2023-05-18T13:58:31.4104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:31.41048+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.815618ms 2023-05-18T13:58:31.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:36.40289+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.868315ms 2023-05-18T13:58:36.40298+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:36.41122+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.203806ms 2023-05-18T13:58:36.41127+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:41.41133+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.419025ms 2023-05-18T13:58:41.41139+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:41.41144+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.797913ms 2023-05-18T13:58:41.41148+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:46.43093+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.443042ms 2023-05-18T13:58:46.43099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:46.43105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=27.107951ms 2023-05-18T13:58:46.43108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:46.45195+08:00 ERROR [539043,7b429a662e941852] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:58:51.41089+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.243906ms 2023-05-18T13:58:51.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:51.41105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.174921ms 2023-05-18T13:58:51.4111+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:56.41062+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.969403ms 2023-05-18T13:58:56.41068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:58:56.41076+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.921119ms 2023-05-18T13:58:56.41081+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:01.41071+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.225006ms 2023-05-18T13:59:01.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:01.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.330124ms 2023-05-18T13:59:01.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:06.41039+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.899302ms 2023-05-18T13:59:06.41045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:06.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.938419ms 2023-05-18T13:59:06.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:11.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.940603ms 2023-05-18T13:59:11.41098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:11.41105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.967019ms 2023-05-18T13:59:11.41108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:16.40199+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.021917ms 2023-05-18T13:59:16.40206+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:16.40998+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.830401ms 2023-05-18T13:59:16.41002+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:16.41068+08:00 ERROR [539043,583d65746c5fa38f] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:59:21.40197+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.964016ms 2023-05-18T13:59:21.40206+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:21.40801+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.292407ms 2023-05-18T13:59:21.40805+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:26.40311+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.118031ms 2023-05-18T13:59:26.40318+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:26.41+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.238707ms 2023-05-18T13:59:26.41005+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:31.41123+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.528011ms 2023-05-18T13:59:31.41129+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:31.41138+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.665829ms 2023-05-18T13:59:31.41142+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:36.40501+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.184544ms 2023-05-18T13:59:36.40507+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:36.41153+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.730613ms 2023-05-18T13:59:36.4116+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:41.4102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.032003ms 2023-05-18T13:59:41.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:41.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.10292ms 2023-05-18T13:59:41.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:46.41885+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.976941ms 2023-05-18T13:59:46.41891+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:46.43447+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=27.173451ms 2023-05-18T13:59:46.43453+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:46.45429+08:00 ERROR [539043,2ed68334e066c4a0] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T13:59:51.41084+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.185306ms 2023-05-18T13:59:51.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:51.41098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.347824ms 2023-05-18T13:59:51.41101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:56.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.237707ms 2023-05-18T13:59:56.41048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T13:59:56.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.322924ms 2023-05-18T13:59:56.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:01.40645+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.456561ms 2023-05-18T14:00:01.40653+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:01.41085+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.944502ms 2023-05-18T14:00:01.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:06.41012+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.163305ms 2023-05-18T14:00:06.41019+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:06.41024+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.214523ms 2023-05-18T14:00:06.41027+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:11.41024+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.173006ms 2023-05-18T14:00:11.41031+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:11.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.202922ms 2023-05-18T14:00:11.41044+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:16.40266+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.923915ms 2023-05-18T14:00:16.40272+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:16.41088+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.110205ms 2023-05-18T14:00:16.41093+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:16.41159+08:00 ERROR [539043,d25c28ed65964798] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:00:16.51826+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields: duration="29.5µs", module=monitor.ob 2023-05-18T14:00:16.51833+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields:, module=monitor.ob, eventType=add, duration="5.8µs" 2023-05-18T14:00:16.51841+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields: duration="5.4µs", module=monitor.ob 2023-05-18T14:00:16.51851+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields: module=monitor.ob, eventType=add, duration="5.7µs" 2023-05-18T14:00:16.51854+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T14:00:16.5257+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc00069e8c0 0xc00069e960 0xc00069ea00 0xc00069eaa0 0xc00069eb40 0xc00069ebe0 0xc00069ec80 0xc00069ed20 0xc00069edc0 0xc00069ee60 0xc00069ef00 0xc00069efa0 0xc00069f040 0xc00069f0e0 0xc00069f180 0xc00069f220 0xc00069f2c0 0xc00069f360 0xc00069f400 0xc00069f4a0 0xc00069f540 0xc00069f5e0 0xc00069f680 0xc00069f720 0xc00069f7c0 0xc00069f860 0xc00069f900 0xc00069f9a0 0xc00069fa40 0xc00069fae0 0xc00069fb80] CollectInterval:1s TimeAlign:false} 2023-05-18T14:00:16.52796+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T14:00:16.528+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields: duration="4.6µs", input=mysqlTableInput 2023-05-18T14:00:16.52806+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields: input=mysqlTableInput, duration="69.401µs" 2023-05-18T14:00:16.52809+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields:, module=monitor.ob, eventType=add, error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)", duration=9.583324ms 2023-05-18T14:00:16.52811+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields:, module=monitor.ob, eventType=add, duration=9.601724ms 2023-05-18T14:00:16.52813+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields:, module=monitor.ob, duration=9.722126ms 2023-05-18T14:00:16.52814+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields:, eventType=add, module=monitor.ob, duration=9.816527ms 2023-05-18T14:00:16.52816+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields: module=monitor.ob, duration=9.920528ms 2023-05-18T14:00:16.52818+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 21 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T14:00:21.41029+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.839702ms 2023-05-18T14:00:21.41036+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:21.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.757916ms 2023-05-18T14:00:21.41045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:26.4109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.356408ms 2023-05-18T14:00:26.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:26.41104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.385524ms 2023-05-18T14:00:26.41108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:31.41066+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.041804ms 2023-05-18T14:00:31.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:31.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.171322ms 2023-05-18T14:00:31.41083+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:36.41324+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.680054ms 2023-05-18T14:00:36.4133+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:36.41456+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.166757ms 2023-05-18T14:00:36.41462+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:41.41051+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.395909ms 2023-05-18T14:00:41.41058+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:41.41066+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.072821ms 2023-05-18T14:00:41.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:46.41607+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.332608ms 2023-05-18T14:00:46.41614+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:46.43473+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=37.286582ms 2023-05-18T14:00:46.43484+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:46.4482+08:00 ERROR [539043,9ef9a9f51fed5f68] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:00:51.4054+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.360747ms 2023-05-18T14:00:51.40549+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:51.41215+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.353508ms 2023-05-18T14:00:51.41221+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:56.41132+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.203206ms 2023-05-18T14:00:56.41139+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:00:56.41148+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.596128ms 2023-05-18T14:00:56.41151+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:01.40313+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.132831ms 2023-05-18T14:01:01.40321+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:01.41041+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.629812ms 2023-05-18T14:01:01.41046+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:06.4122+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.902444ms 2023-05-18T14:01:06.41227+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:06.41234+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.013616ms 2023-05-18T14:01:06.41237+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:11.4132+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.319449ms 2023-05-18T14:01:11.41327+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:11.41427+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.590811ms 2023-05-18T14:01:11.41432+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:16.40556+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.865354ms 2023-05-18T14:01:16.40566+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:16.40572+08:00 ERROR [539043,6d75cf877fa67a4c] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:01:16.41312+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.435509ms 2023-05-18T14:01:16.41318+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:21.41308+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.233106ms 2023-05-18T14:01:21.41319+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:21.41323+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=20.07916ms 2023-05-18T14:01:21.41325+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:26.41102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.031703ms 2023-05-18T14:01:26.41109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:26.41118+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.165621ms 2023-05-18T14:01:26.41121+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:31.40415+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.287933ms 2023-05-18T14:01:31.40421+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:31.41133+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.435409ms 2023-05-18T14:01:31.41159+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:36.40949+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.380712ms 2023-05-18T14:01:36.40956+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:36.41101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.385809ms 2023-05-18T14:01:36.41106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:41.41109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.375008ms 2023-05-18T14:01:41.41116+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:41.41123+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.383324ms 2023-05-18T14:01:41.41126+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:46.43492+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=25.907335ms 2023-05-18T14:01:46.43499+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:46.43509+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.587444ms 2023-05-18T14:01:46.43512+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:46.45678+08:00 ERROR [539043,d2191cfb428fe8e9] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:01:51.40961+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.817001ms 2023-05-18T14:01:51.40967+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:51.40977+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.600615ms 2023-05-18T14:01:51.4098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:56.41321+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=20.009558ms 2023-05-18T14:01:56.41327+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:01:56.41489+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.930967ms 2023-05-18T14:01:56.41494+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:01.40551+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=12.197058ms 2023-05-18T14:02:01.4056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:01.41238+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.163132ms 2023-05-18T14:02:01.41243+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:06.41+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.530897ms 2023-05-18T14:02:06.41006+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:06.41013+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.300911ms 2023-05-18T14:02:06.41017+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:11.40163+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.50301ms 2023-05-18T14:02:11.402+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:11.413+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.682638ms 2023-05-18T14:02:11.41306+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:16.40241+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.709112ms 2023-05-18T14:02:16.40247+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:16.41022+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.707099ms 2023-05-18T14:02:16.41027+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:16.41094+08:00 ERROR [539043,0488f335c93eb337] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:02:21.41074+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.853301ms 2023-05-18T14:02:21.41082+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:21.41089+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.966219ms 2023-05-18T14:02:21.41092+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:26.4075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.624976ms 2023-05-18T14:02:26.4076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:26.41066+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.274907ms 2023-05-18T14:02:26.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:31.4109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.414808ms 2023-05-18T14:02:31.41098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:31.41107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.568026ms 2023-05-18T14:02:31.41111+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:36.40543+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.534349ms 2023-05-18T14:02:36.40552+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:36.41067+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.001403ms 2023-05-18T14:02:36.41072+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:41.41325+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.172606ms 2023-05-18T14:02:41.41332+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:41.41342+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=19.665854ms 2023-05-18T14:02:41.41347+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:46.42553+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.093018ms 2023-05-18T14:02:46.42563+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:46.43439+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.676212ms 2023-05-18T14:02:46.43444+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:46.46167+08:00 ERROR [539043,597cdec7552ca9bf] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:02:51.4112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.355208ms 2023-05-18T14:02:51.41127+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:51.41134+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.697928ms 2023-05-18T14:02:51.41137+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:56.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.173305ms 2023-05-18T14:02:56.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:02:56.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.239122ms 2023-05-18T14:02:56.41075+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:01.40824+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.208584ms 2023-05-18T14:03:01.40831+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:01.41346+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.221006ms 2023-05-18T14:03:01.41352+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:06.40312+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.128231ms 2023-05-18T14:03:06.40319+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:06.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.579111ms 2023-05-18T14:03:06.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:11.41123+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.336724ms 2023-05-18T14:03:11.41129+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:11.41134+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.417909ms 2023-05-18T14:03:11.41137+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:16.40209+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.745613ms 2023-05-18T14:03:16.40232+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:16.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.291807ms 2023-05-18T14:03:16.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:16.41152+08:00 ERROR [539043,14ae7a04a48d9929] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:03:21.41085+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.074505ms 2023-05-18T14:03:21.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:21.41098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.07862ms 2023-05-18T14:03:21.41102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:26.41087+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.362808ms 2023-05-18T14:03:26.41093+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:26.411+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.182422ms 2023-05-18T14:03:26.41104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:31.40179+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.694312ms 2023-05-18T14:03:31.40185+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:31.40772+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.015603ms 2023-05-18T14:03:31.40778+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:36.41014+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.026104ms 2023-05-18T14:03:36.41021+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:36.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.98002ms 2023-05-18T14:03:36.4103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:41.41186+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.579623ms 2023-05-18T14:03:41.41195+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:41.41204+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.695941ms 2023-05-18T14:03:41.41207+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:46.42846+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=31.74621ms 2023-05-18T14:03:46.43652+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:46.45405+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=26.175238ms 2023-05-18T14:03:46.45412+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:46.47002+08:00 ERROR [539043,7ad3d439cf4e5f51] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:03:51.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.978303ms 2023-05-18T14:03:51.4105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:51.41059+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.126821ms 2023-05-18T14:03:51.41063+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:56.40309+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.12733ms 2023-05-18T14:03:56.40325+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:03:56.4095+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.906402ms 2023-05-18T14:03:56.40956+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:01.4044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.394834ms 2023-05-18T14:04:01.40447+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:01.41066+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.063704ms 2023-05-18T14:04:01.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:06.41081+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.983803ms 2023-05-18T14:04:06.41087+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:06.41095+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.01332ms 2023-05-18T14:04:06.41099+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:11.40275+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.983816ms 2023-05-18T14:04:11.40281+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:11.41119+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.339308ms 2023-05-18T14:04:11.41123+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:16.40232+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.864315ms 2023-05-18T14:04:16.40238+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:16.41006+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.634199ms 2023-05-18T14:04:16.41011+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:16.41077+08:00 ERROR [539043,81d87320bfa1b7f7] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:04:21.40998+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.7311ms 2023-05-18T14:04:21.41005+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:21.41014+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.499013ms 2023-05-18T14:04:21.41017+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:26.40304+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.010516ms 2023-05-18T14:04:26.4031+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:26.41098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.834801ms 2023-05-18T14:04:26.41104+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:31.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.909518ms 2023-05-18T14:04:31.41053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:31.41059+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.056404ms 2023-05-18T14:04:31.41063+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:36.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.901202ms 2023-05-18T14:04:36.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:36.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.082721ms 2023-05-18T14:04:36.41076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:41.40999+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.697099ms 2023-05-18T14:04:41.41006+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:41.41013+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.717716ms 2023-05-18T14:04:41.41016+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:46.43431+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=26.972049ms 2023-05-18T14:04:46.43437+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:46.43453+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=26.726545ms 2023-05-18T14:04:46.43456+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:46.4553+08:00 ERROR [539043,5be337c4a3e69642] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:04:51.40982+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.005103ms 2023-05-18T14:04:51.40989+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:51.40993+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.917919ms 2023-05-18T14:04:51.40996+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:56.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.321508ms 2023-05-18T14:04:56.41083+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:04:56.4109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.345824ms 2023-05-18T14:04:56.41092+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:01.41001+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.831501ms 2023-05-18T14:05:01.41019+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.827217ms 2023-05-18T14:05:01.41023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:01.4101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:06.40174+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.791013ms 2023-05-18T14:05:06.4018+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:06.40817+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.57501ms 2023-05-18T14:05:06.40821+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:11.40731+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=13.391573ms 2023-05-18T14:05:11.4074+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:11.41082+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.083005ms 2023-05-18T14:05:11.41087+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:16.40188+08:00 ERROR [539043,10c4b03e524656c1] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:05:16.40279+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.765813ms 2023-05-18T14:05:16.40284+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:16.40899+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.390208ms 2023-05-18T14:05:16.40905+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:21.40224+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.224219ms 2023-05-18T14:05:21.4023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:21.40998+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.610598ms 2023-05-18T14:05:21.41004+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:26.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.945519ms 2023-05-18T14:05:26.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:26.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.049704ms 2023-05-18T14:05:26.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:31.41009+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.581598ms 2023-05-18T14:05:31.41015+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:31.41023+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.636915ms 2023-05-18T14:05:31.41028+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:36.41029+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.197105ms 2023-05-18T14:05:36.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:36.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.272423ms 2023-05-18T14:05:36.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:41.41001+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.291907ms 2023-05-18T14:05:41.41007+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:41.41014+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.939319ms 2023-05-18T14:05:41.41017+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:46.44339+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=35.509858ms 2023-05-18T14:05:46.44346+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:46.44351+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=36.144567ms 2023-05-18T14:05:46.44353+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:46.4598+08:00 ERROR [539043,3c8d485353a654f2] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:05:51.41126+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.384708ms 2023-05-18T14:05:51.41134+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:51.41141+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.463925ms 2023-05-18T14:05:51.41144+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:56.41022+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.139805ms 2023-05-18T14:05:56.41028+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:05:56.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.079321ms 2023-05-18T14:05:56.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:01.41133+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.032303ms 2023-05-18T14:06:01.41139+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:01.41148+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.574227ms 2023-05-18T14:06:01.4115+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:06.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.991603ms 2023-05-18T14:06:06.4106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:06.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.854718ms 2023-05-18T14:06:06.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:11.41327+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.241749ms 2023-05-18T14:06:11.41334+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:11.4136+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.455009ms 2023-05-18T14:06:11.41365+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:16.40248+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.729213ms 2023-05-18T14:06:16.40255+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:16.41084+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.229806ms 2023-05-18T14:06:16.41088+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:16.41156+08:00 ERROR [539043,181c71efc07fb52c] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:06:21.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.103705ms 2023-05-18T14:06:21.41094+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:21.41101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.159022ms 2023-05-18T14:06:21.41106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:26.4031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.104418ms 2023-05-18T14:06:26.40317+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:26.40795+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.075804ms 2023-05-18T14:06:26.408+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:31.40969+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.040704ms 2023-05-18T14:06:31.40975+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:31.40988+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.703715ms 2023-05-18T14:06:31.40992+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:36.40807+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.585688ms 2023-05-18T14:06:36.40813+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:36.41028+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.936403ms 2023-05-18T14:06:36.41034+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:41.40227+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.811313ms 2023-05-18T14:06:41.40234+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:41.40856+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.335208ms 2023-05-18T14:06:41.40866+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:46.41745+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.347908ms 2023-05-18T14:06:46.41753+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:46.41763+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.401125ms 2023-05-18T14:06:46.41766+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:46.44144+08:00 ERROR [539043,70689d4cd12f5950] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:06:46.47924+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 1753264 fields:, error="open /proc/1753264/status: no such file or directory" 2023-05-18T14:06:46.47929+08:00 WARN [539043,] caller=common/input_cache.go:115:refreshProcesses: failed to get process name of pid: 1753281 fields:, error="open /proc/1753281/status: no such file or directory" 2023-05-18T14:06:51.40566+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.462361ms 2023-05-18T14:06:51.40572+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:51.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.385309ms 2023-05-18T14:06:51.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:56.41051+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.142605ms 2023-05-18T14:06:56.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:06:56.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.978019ms 2023-05-18T14:06:56.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:01.40266+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.807714ms 2023-05-18T14:07:01.40273+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:01.41055+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.786001ms 2023-05-18T14:07:01.41062+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:06.41105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.08992ms 2023-05-18T14:07:06.41112+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:06.41117+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.176806ms 2023-05-18T14:07:06.41122+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:11.41088+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.224006ms 2023-05-18T14:07:11.41095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:11.41103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.115821ms 2023-05-18T14:07:11.41106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:16.4052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.662151ms 2023-05-18T14:07:16.40527+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:16.41372+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.414309ms 2023-05-18T14:07:16.41377+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:16.41442+08:00 ERROR [539043,fe3ad9ca297db472] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:07:21.40266+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.679625ms 2023-05-18T14:07:21.40272+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:21.40775+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.155605ms 2023-05-18T14:07:21.4078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:26.40993+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.890102ms 2023-05-18T14:07:26.41+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:26.41008+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.892718ms 2023-05-18T14:07:26.41011+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:31.40973+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.611899ms 2023-05-18T14:07:31.4098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:31.40986+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.709615ms 2023-05-18T14:07:31.40989+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:36.40493+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.534449ms 2023-05-18T14:07:36.40499+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:36.41089+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.694212ms 2023-05-18T14:07:36.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:41.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.217406ms 2023-05-18T14:07:41.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:41.41088+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.707929ms 2023-05-18T14:07:41.41091+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:46.41547+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=11.743552ms 2023-05-18T14:07:46.41553+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:46.41561+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.40816ms 2023-05-18T14:07:46.41565+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:46.42913+08:00 ERROR [539043,4f85718e73dab7e7] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:07:51.41042+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.632215ms 2023-05-18T14:07:51.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:51.41079+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.154005ms 2023-05-18T14:07:51.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:56.40996+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.967003ms 2023-05-18T14:07:56.41003+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:07:56.41011+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.946819ms 2023-05-18T14:07:56.41014+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:01.40859+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=14.934793ms 2023-05-18T14:08:01.40865+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:01.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.066804ms 2023-05-18T14:08:01.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:06.41022+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.858602ms 2023-05-18T14:08:06.41029+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:06.41036+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.99412ms 2023-05-18T14:08:06.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:11.4107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.048104ms 2023-05-18T14:08:11.41076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:11.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.828617ms 2023-05-18T14:08:11.4109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:16.4023+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.101618ms 2023-05-18T14:08:16.40237+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:16.4102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.800201ms 2023-05-18T14:08:16.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:16.41092+08:00 ERROR [539043,c07a449270bc3f33] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:08:21.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.015103ms 2023-05-18T14:08:21.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:21.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.166422ms 2023-05-18T14:08:21.41048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:26.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.599111ms 2023-05-18T14:08:26.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:26.41066+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.316324ms 2023-05-18T14:08:26.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:31.40632+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.350272ms 2023-05-18T14:08:31.40638+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:31.40944+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.666699ms 2023-05-18T14:08:31.40949+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:36.41006+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.856901ms 2023-05-18T14:08:36.41012+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:36.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.683615ms 2023-05-18T14:08:36.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:41.40264+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.878115ms 2023-05-18T14:08:41.4027+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:41.4109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.132605ms 2023-05-18T14:08:41.41095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:46.43337+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=27.007649ms 2023-05-18T14:08:46.43344+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:46.4335+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.547743ms 2023-05-18T14:08:46.43352+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:46.45563+08:00 ERROR [539043,ccd6b057d34c0fe2] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:08:51.40315+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.096331ms 2023-05-18T14:08:51.40323+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:51.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.274007ms 2023-05-18T14:08:51.41045+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:56.41016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.49491ms 2023-05-18T14:08:56.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:08:56.41027+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.271924ms 2023-05-18T14:08:56.4103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:01.40647+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.14647ms 2023-05-18T14:09:01.40656+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:01.40997+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.010004ms 2023-05-18T14:09:01.41001+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:06.40957+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.687099ms 2023-05-18T14:09:06.40965+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:06.40974+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.496313ms 2023-05-18T14:09:06.40977+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:11.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.095205ms 2023-05-18T14:09:11.41023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:11.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.932518ms 2023-05-18T14:09:11.41033+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:16.4022+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.078418ms 2023-05-18T14:09:16.40226+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:16.40994+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.646799ms 2023-05-18T14:09:16.40998+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:16.41068+08:00 ERROR [539043,583c00a68020543d] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:09:21.41149+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.577911ms 2023-05-18T14:09:21.41156+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:21.41166+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.712729ms 2023-05-18T14:09:21.4117+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:26.40992+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.891302ms 2023-05-18T14:09:26.41+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:26.41009+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.875418ms 2023-05-18T14:09:26.41012+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:31.41025+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.901402ms 2023-05-18T14:09:31.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:31.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.832417ms 2023-05-18T14:09:31.41043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:36.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.021903ms 2023-05-18T14:09:36.41095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:36.41104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.224322ms 2023-05-18T14:09:36.41107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:41.4099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.828101ms 2023-05-18T14:09:41.40997+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:41.41005+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.815018ms 2023-05-18T14:09:41.41008+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:46.40673+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.073517ms 2023-05-18T14:09:46.40679+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:46.41503+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.194406ms 2023-05-18T14:09:46.41508+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:46.44667+08:00 ERROR [539043,6f3790639fdc778a] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:09:51.40937+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.356011ms 2023-05-18T14:09:51.40945+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:51.40955+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.8062ms 2023-05-18T14:09:51.40959+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:56.41071+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.180006ms 2023-05-18T14:09:56.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:09:56.41086+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.848218ms 2023-05-18T14:09:56.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:01.40849+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=14.770491ms 2023-05-18T14:10:01.40856+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:01.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.834801ms 2023-05-18T14:10:01.41063+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:06.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.991603ms 2023-05-18T14:10:06.41023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:06.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.912819ms 2023-05-18T14:10:06.41034+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:11.41055+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.957103ms 2023-05-18T14:10:11.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:11.41071+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.809517ms 2023-05-18T14:10:11.41074+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:16.40268+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.456022ms 2023-05-18T14:10:16.40274+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:16.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.854001ms 2023-05-18T14:10:16.41068+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:16.41136+08:00 ERROR [539043,60c36be81b930a98] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:10:16.52897+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields:, module=monitor.ob, duration="23.801µs" 2023-05-18T14:10:16.52905+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields: eventType=add, duration="17.201µs", module=monitor.ob 2023-05-18T14:10:16.52908+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields:, module=monitor.ob, duration="5.2µs" 2023-05-18T14:10:16.52912+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields: module=monitor.ob, eventType=add, duration="6.101µs" 2023-05-18T14:10:16.52915+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T14:10:16.53294+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc0009fe640 0xc0009fe6e0 0xc0009fe780 0xc0009fe820 0xc0009fe8c0 0xc0009fe960 0xc0009fea00 0xc0009feaa0 0xc0009feb40 0xc0009febe0 0xc0009fec80 0xc0009fed20 0xc0009fedc0 0xc0009fee60 0xc0009fef00 0xc0009fefa0 0xc0009ff040 0xc0009ff0e0 0xc0009ff180 0xc0009ff220 0xc0009ff2c0 0xc0009ff360 0xc0009ff400 0xc0009ff4a0 0xc0009ff540 0xc0009ff5e0 0xc0009ff680 0xc0009ff720 0xc0009ff7c0 0xc0009ff860 0xc0009ff900] CollectInterval:1s TimeAlign:false} 2023-05-18T14:10:16.53423+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T14:10:16.53426+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields: input=mysqlTableInput, duration="4.4µs" 2023-05-18T14:10:16.53428+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields:, input=mysqlTableInput, duration="25.4µs" 2023-05-18T14:10:16.5343+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields:, module=monitor.ob, eventType=add, error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)", duration=5.185267ms 2023-05-18T14:10:16.53432+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields: eventType=add, duration=5.203368ms, module=monitor.ob 2023-05-18T14:10:16.53434+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields:, module=monitor.ob, duration=5.259568ms 2023-05-18T14:10:16.53435+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields:, module=monitor.ob, eventType=add, duration=5.312969ms 2023-05-18T14:10:16.53436+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields:, module=monitor.ob, duration=5.41357ms 2023-05-18T14:10:16.53438+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 22 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T14:10:21.41057+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.882201ms 2023-05-18T14:10:21.41065+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:21.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.698215ms 2023-05-18T14:10:21.41075+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:26.41007+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.623999ms 2023-05-18T14:10:26.41013+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:26.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.294411ms 2023-05-18T14:10:26.41025+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:31.41035+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.879602ms 2023-05-18T14:10:31.41042+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:31.41049+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.906218ms 2023-05-18T14:10:31.41052+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:36.4016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.604111ms 2023-05-18T14:10:36.40167+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:36.40782+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.139905ms 2023-05-18T14:10:36.40787+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:41.40519+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.851953ms 2023-05-18T14:10:41.40527+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:41.41016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.164206ms 2023-05-18T14:10:41.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:46.43139+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.991249ms 2023-05-18T14:10:46.43145+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:46.43155+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.691145ms 2023-05-18T14:10:46.43159+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:46.44504+08:00 ERROR [539043,e8d3deb14c714115] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:10:51.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.884302ms 2023-05-18T14:10:51.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:51.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.854318ms 2023-05-18T14:10:51.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:56.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.108005ms 2023-05-18T14:10:56.41038+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:10:56.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.322424ms 2023-05-18T14:10:56.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:01.41096+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.069604ms 2023-05-18T14:11:01.41103+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:01.41112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.489726ms 2023-05-18T14:11:01.41114+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:06.41038+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.081905ms 2023-05-18T14:11:06.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:06.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.242223ms 2023-05-18T14:11:06.4106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:11.40993+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.560998ms 2023-05-18T14:11:11.40999+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:11.41009+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.465513ms 2023-05-18T14:11:11.41012+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:16.40217+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.199619ms 2023-05-18T14:11:16.40224+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:16.4023+08:00 ERROR [539043,9b65d8cdfa9113e3] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:11:16.40865+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.057817ms 2023-05-18T14:11:16.40871+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:21.41098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.228606ms 2023-05-18T14:11:21.41105+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:21.41112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.178722ms 2023-05-18T14:11:21.41116+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:26.4026+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.921215ms 2023-05-18T14:11:26.40267+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:26.40853+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.180105ms 2023-05-18T14:11:26.40859+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:31.41169+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.476009ms 2023-05-18T14:11:31.41176+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:31.41183+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.82983ms 2023-05-18T14:11:31.41186+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:36.41083+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.164805ms 2023-05-18T14:11:36.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:36.41098+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.307123ms 2023-05-18T14:11:36.41101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:41.4058+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.584762ms 2023-05-18T14:11:41.40586+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:41.41044+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.301907ms 2023-05-18T14:11:41.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:46.42726+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=27.89096ms 2023-05-18T14:11:46.42733+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:46.42738+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=27.549356ms 2023-05-18T14:11:46.42741+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:46.44105+08:00 ERROR [539043,efe06d68959740d2] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:11:51.4107+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.05982ms 2023-05-18T14:11:51.41077+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:51.41082+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.376509ms 2023-05-18T14:11:51.41085+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:56.40988+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.678515ms 2023-05-18T14:11:56.40997+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:11:56.41002+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.967903ms 2023-05-18T14:11:56.41005+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:01.41328+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.902257ms 2023-05-18T14:12:01.41334+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:01.41562+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=13.553475ms 2023-05-18T14:12:01.41567+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:06.40194+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.961116ms 2023-05-18T14:12:06.40224+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:06.40786+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.272907ms 2023-05-18T14:12:06.40791+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:11.41037+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.809701ms 2023-05-18T14:12:11.41044+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:11.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.660515ms 2023-05-18T14:12:11.41055+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:16.40381+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=10.187732ms 2023-05-18T14:12:16.40397+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:16.41188+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.828701ms 2023-05-18T14:12:16.41194+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:16.4127+08:00 ERROR [539043,514ac213f57b3fce] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:12:21.41059+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.028303ms 2023-05-18T14:12:21.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:21.41075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.05522ms 2023-05-18T14:12:21.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:26.40212+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.842114ms 2023-05-18T14:12:26.40219+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:26.40803+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.103504ms 2023-05-18T14:12:26.40808+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:31.40217+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.719213ms 2023-05-18T14:12:31.40224+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:31.40844+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.331808ms 2023-05-18T14:12:31.40849+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:36.41017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.7649ms 2023-05-18T14:12:36.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:36.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.921019ms 2023-05-18T14:12:36.41034+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:41.4102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.897602ms 2023-05-18T14:12:41.41026+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:41.41033+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.630114ms 2023-05-18T14:12:41.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:46.41826+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.828853ms 2023-05-18T14:12:46.41835+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:46.41846+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.574949ms 2023-05-18T14:12:46.4185+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:46.43355+08:00 ERROR [539043,0c3e904195259c08] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:12:51.41202+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.120005ms 2023-05-18T14:12:51.4121+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:51.41218+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.439438ms 2023-05-18T14:12:51.41221+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:56.41201+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.576223ms 2023-05-18T14:12:56.41209+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:12:56.4122+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=18.434738ms 2023-05-18T14:12:56.41223+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:01.41089+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.350808ms 2023-05-18T14:13:01.41095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:01.41102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.422225ms 2023-05-18T14:13:01.41106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:06.4109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.175704ms 2023-05-18T14:13:06.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:06.41105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.33072ms 2023-05-18T14:13:06.41109+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:11.41089+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.142903ms 2023-05-18T14:13:11.41096+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:11.41105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.238218ms 2023-05-18T14:13:11.41108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:16.40286+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.321718ms 2023-05-18T14:13:16.40293+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:16.41126+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.284206ms 2023-05-18T14:13:16.41132+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:16.412+08:00 ERROR [539043,64614517dcee5036] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:13:21.41009+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.8738ms 2023-05-18T14:13:21.41015+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:21.41023+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.736612ms 2023-05-18T14:13:21.41025+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:26.40193+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.69421ms 2023-05-18T14:13:26.40199+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:26.40819+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.320006ms 2023-05-18T14:13:26.40831+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:31.40578+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.130353ms 2023-05-18T14:13:31.40584+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:31.41051+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.067802ms 2023-05-18T14:13:31.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:36.40989+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.758298ms 2023-05-18T14:13:36.40997+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:36.41004+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.869314ms 2023-05-18T14:13:36.41007+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:41.41081+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.082202ms 2023-05-18T14:13:41.41089+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:41.41099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.200019ms 2023-05-18T14:13:41.41102+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:46.40581+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.367618ms 2023-05-18T14:13:46.40588+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:46.41403+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.120103ms 2023-05-18T14:13:46.41408+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:46.44869+08:00 ERROR [539043,ac26d35699860fd0] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:13:51.41038+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.402107ms 2023-05-18T14:13:51.41047+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:51.41055+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.389421ms 2023-05-18T14:13:51.41059+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:56.40995+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.160204ms 2023-05-18T14:13:56.41002+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:13:56.41009+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.957815ms 2023-05-18T14:13:56.41012+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:01.4104+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.634197ms 2023-05-18T14:14:01.41046+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:01.41053+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.50581ms 2023-05-18T14:14:01.41056+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:06.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.631511ms 2023-05-18T14:14:06.41052+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:06.4109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.184504ms 2023-05-18T14:14:06.41094+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:11.40416+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.02124ms 2023-05-18T14:14:11.40423+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:11.41026+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.844199ms 2023-05-18T14:14:11.41031+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:16.40277+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.238817ms 2023-05-18T14:14:16.40284+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:16.41047+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.584596ms 2023-05-18T14:14:16.41053+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:16.41122+08:00 ERROR [539043,8899abbf2db03c94] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:14:21.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.022702ms 2023-05-18T14:14:21.41037+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:21.41045+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.825714ms 2023-05-18T14:14:21.41048+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:26.4112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.191404ms 2023-05-18T14:14:26.41126+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:26.41135+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.910427ms 2023-05-18T14:14:26.41139+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:31.411+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.267105ms 2023-05-18T14:14:31.41106+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:31.41114+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.38442ms 2023-05-18T14:14:31.41118+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:36.41105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.410807ms 2023-05-18T14:14:36.41112+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:36.4112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.453621ms 2023-05-18T14:14:36.41123+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:41.40605+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.554559ms 2023-05-18T14:14:41.40612+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:41.41116+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.128703ms 2023-05-18T14:14:41.41122+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:46.41597+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.70791ms 2023-05-18T14:14:46.41603+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:46.4239+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.801999ms 2023-05-18T14:14:46.42397+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:46.45172+08:00 ERROR [539043,d777021023e9cac8] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:14:51.41009+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.826599ms 2023-05-18T14:14:51.41015+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:51.41022+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.574311ms 2023-05-18T14:14:51.41025+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:56.4111+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.964113ms 2023-05-18T14:14:56.41116+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:14:56.41127+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.120129ms 2023-05-18T14:14:56.41131+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:01.4105+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.112003ms 2023-05-18T14:15:01.41057+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:01.41066+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.088617ms 2023-05-18T14:15:01.41069+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:06.40294+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.901613ms 2023-05-18T14:15:06.40302+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:06.4078+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.195504ms 2023-05-18T14:15:06.40785+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:11.40982+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.716497ms 2023-05-18T14:15:11.40988+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:11.40995+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.769513ms 2023-05-18T14:15:11.40998+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:16.40275+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.807111ms 2023-05-18T14:15:16.40282+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:16.41237+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.51882ms 2023-05-18T14:15:16.41243+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:16.41314+08:00 ERROR [539043,c42a27bb90819ba5] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:15:21.40447+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.157542ms 2023-05-18T14:15:21.40453+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:21.41003+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.933601ms 2023-05-18T14:15:21.41008+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:26.40195+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.539808ms 2023-05-18T14:15:26.40203+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:26.40814+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.181504ms 2023-05-18T14:15:26.40818+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:31.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.234204ms 2023-05-18T14:15:31.41074+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:31.41081+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.191118ms 2023-05-18T14:15:31.41084+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:36.41071+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.264319ms 2023-05-18T14:15:36.41076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:36.41064+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.165803ms 2023-05-18T14:15:36.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:41.41322+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=19.412546ms 2023-05-18T14:15:41.41329+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:41.41417+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.118616ms 2023-05-18T14:15:41.41422+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:46.41552+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.077415ms 2023-05-18T14:15:46.4156+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:46.44157+08:00 ERROR [539043,2a63cc6ad7aa6a06] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:15:46.44171+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=26.02873ms 2023-05-18T14:15:46.44175+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:51.41001+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.679998ms 2023-05-18T14:15:51.41007+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:51.41014+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.500509ms 2023-05-18T14:15:51.41017+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:56.40312+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.131429ms 2023-05-18T14:15:56.40318+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:15:56.41028+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.212405ms 2023-05-18T14:15:56.41033+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:01.40526+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.87215ms 2023-05-18T14:16:01.40532+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:01.4131+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.745298ms 2023-05-18T14:16:01.41315+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:06.40973+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.809699ms 2023-05-18T14:16:06.4098+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:06.40988+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.489909ms 2023-05-18T14:16:06.40991+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:11.41129+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.65251ms 2023-05-18T14:16:11.41135+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:11.41146+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.608623ms 2023-05-18T14:16:11.41149+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:16.40272+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.854313ms 2023-05-18T14:16:16.40278+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:16.41106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.231704ms 2023-05-18T14:16:16.41111+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:16.41179+08:00 ERROR [539043,0e4048f010d0cc6d] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:16:21.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.845099ms 2023-05-18T14:16:21.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:21.41075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.121417ms 2023-05-18T14:16:21.41077+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:26.40993+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.317505ms 2023-05-18T14:16:26.40999+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:26.41005+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.030316ms 2023-05-18T14:16:26.41008+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:31.40966+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.608996ms 2023-05-18T14:16:31.40973+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:31.40981+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.328007ms 2023-05-18T14:16:31.40984+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:36.40999+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.957601ms 2023-05-18T14:16:36.41005+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:36.41012+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.026816ms 2023-05-18T14:16:36.41015+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:41.41075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.468807ms 2023-05-18T14:16:41.41082+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:41.4109+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.576123ms 2023-05-18T14:16:41.41093+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:46.43197+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=32.246509ms 2023-05-18T14:16:46.43203+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:46.4576+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=26.138932ms 2023-05-18T14:16:46.45766+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:46.4702+08:00 ERROR [539043,f7fea2dc4665dc84] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:16:51.41016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.855499ms 2023-05-18T14:16:51.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:51.41029+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.012316ms 2023-05-18T14:16:51.41032+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:56.41031+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.743298ms 2023-05-18T14:16:56.41039+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:16:56.41046+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.760413ms 2023-05-18T14:16:56.41049+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:01.41006+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.930401ms 2023-05-18T14:17:01.41011+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:01.41019+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.973515ms 2023-05-18T14:17:01.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:06.41164+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.711611ms 2023-05-18T14:17:06.4117+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:06.41178+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.983128ms 2023-05-18T14:17:06.41181+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:11.40935+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.670497ms 2023-05-18T14:17:11.40941+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:11.40947+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.49861ms 2023-05-18T14:17:11.4095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:16.40219+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.076415ms 2023-05-18T14:17:16.40225+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:16.41005+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.766298ms 2023-05-18T14:17:16.41009+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:16.41082+08:00 ERROR [539043,94c12483fff44397] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:17:21.41121+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.957401ms 2023-05-18T14:17:21.41128+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:21.41139+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.870927ms 2023-05-18T14:17:21.41142+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:26.41009+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.967701ms 2023-05-18T14:17:26.41016+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:26.41025+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.915215ms 2023-05-18T14:17:26.41028+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:31.40186+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.814512ms 2023-05-18T14:17:31.40194+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:31.40874+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.131503ms 2023-05-18T14:17:31.40879+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:36.4111+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.662424ms 2023-05-18T14:17:36.41116+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:36.4112+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.741811ms 2023-05-18T14:17:36.41123+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:41.40997+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.131703ms 2023-05-18T14:17:41.41003+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:41.41011+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.884414ms 2023-05-18T14:17:41.41014+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:46.42318+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=15.951002ms 2023-05-18T14:17:46.42327+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:46.43348+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=10.873137ms 2023-05-18T14:17:46.43354+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:46.45166+08:00 ERROR [539043,10b0c184e061efd0] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:17:51.41116+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.600909ms 2023-05-18T14:17:51.41122+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:51.41131+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.639824ms 2023-05-18T14:17:51.41135+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:56.40422+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.04554ms 2023-05-18T14:17:56.40429+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:17:56.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.643697ms 2023-05-18T14:17:56.41073+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:01.4017+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.412007ms 2023-05-18T14:18:01.40177+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:01.41447+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=12.669861ms 2023-05-18T14:18:01.41453+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:06.41201+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=18.313732ms 2023-05-18T14:18:06.41207+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:06.41216+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.588122ms 2023-05-18T14:18:06.41219+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:11.41016+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.696797ms 2023-05-18T14:18:11.41025+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:11.41032+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.321007ms 2023-05-18T14:18:11.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:16.40271+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=9.151016ms 2023-05-18T14:18:16.40278+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:16.41065+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.8363ms 2023-05-18T14:18:16.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:16.41134+08:00 ERROR [539043,0d7ca4a0a5ec4df4] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:18:21.40993+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.849399ms 2023-05-18T14:18:21.40999+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:21.41007+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.789913ms 2023-05-18T14:18:21.4101+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:26.40947+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.788199ms 2023-05-18T14:18:26.40954+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:26.40963+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.508909ms 2023-05-18T14:18:26.40967+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:31.40976+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.647597ms 2023-05-18T14:18:31.40982+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:31.4099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.586911ms 2023-05-18T14:18:31.40993+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:36.4055+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=11.685048ms 2023-05-18T14:18:36.40561+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:36.41047+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.000502ms 2023-05-18T14:18:36.41054+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:41.41009+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.839399ms 2023-05-18T14:18:41.41016+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:41.41025+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.944515ms 2023-05-18T14:18:41.41029+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:46.45519+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=26.361735ms 2023-05-18T14:18:46.45525+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:46.45531+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=25.979229ms 2023-05-18T14:18:46.45534+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:46.46353+08:00 ERROR [539043,8a6bbaf99f5d03c3] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:18:51.40235+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.956014ms 2023-05-18T14:18:51.40241+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:51.40811+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.113903ms 2023-05-18T14:18:51.40816+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:56.41002+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.8394ms 2023-05-18T14:18:56.41009+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:18:56.41018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.040716ms 2023-05-18T14:18:56.41023+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:01.41169+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.258504ms 2023-05-18T14:19:01.41175+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:01.41185+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.869726ms 2023-05-18T14:19:01.41189+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:06.41144+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.394407ms 2023-05-18T14:19:06.4115+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:06.41161+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.613324ms 2023-05-18T14:19:06.41165+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:11.41034+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.613996ms 2023-05-18T14:19:11.41043+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:11.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.650011ms 2023-05-18T14:19:11.41055+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:16.40221+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.907313ms 2023-05-18T14:19:16.40227+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:16.4099+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.588296ms 2023-05-18T14:19:16.40994+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:16.41059+08:00 ERROR [539043,a3b4c42f2121b1e6] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:19:21.40987+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.815799ms 2023-05-18T14:19:21.40994+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:21.41002+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.840714ms 2023-05-18T14:19:21.41004+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:26.41006+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.987401ms 2023-05-18T14:19:26.41014+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:26.41021+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.063916ms 2023-05-18T14:19:26.41024+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:31.41073+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.175504ms 2023-05-18T14:19:31.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:31.41091+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.448821ms 2023-05-18T14:19:31.41095+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:36.41063+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.529108ms 2023-05-18T14:19:36.4107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:36.41077+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.583823ms 2023-05-18T14:19:36.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:41.41056+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.121503ms 2023-05-18T14:19:41.41064+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:41.41072+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.212818ms 2023-05-18T14:19:41.41076+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:46.41699+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=9.44642ms 2023-05-18T14:19:46.41705+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:46.42518+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.050502ms 2023-05-18T14:19:46.42523+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:46.45182+08:00 ERROR [539043,8a8167c16c29679d] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields:, error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:19:51.41052+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.162303ms 2023-05-18T14:19:51.41061+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:51.41068+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.166417ms 2023-05-18T14:19:51.41071+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:56.41+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.872ms 2023-05-18T14:19:56.41008+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:19:56.41018+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.888415ms 2023-05-18T14:19:56.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:20:01.41102+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.969401ms 2023-05-18T14:20:01.4111+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:20:01.41119+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.214218ms 2023-05-18T14:20:01.41123+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:20:06.40149+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.524108ms 2023-05-18T14:20:06.40155+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:20:06.40761+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.050702ms 2023-05-18T14:20:06.40765+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:20:11.4106+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.078402ms 2023-05-18T14:20:11.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:20:11.41075+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=17.284619ms 2023-05-18T14:20:11.41078+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:20:16.40203+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.834812ms 2023-05-18T14:20:16.40209+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:20:16.4103+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=8.177204ms 2023-05-18T14:20:16.41035+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:20:16.41152+08:00 ERROR [539043,58833e4f458d5fba] caller=obcommon/connectivity.go:138:doCollect: target oceanbase cannot connect fields: error="Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)" 2023-05-18T14:20:16.53505+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:29:addPipeline: add pipeline module config event fields: module=monitor.ob, duration="23.4µs" 2023-05-18T14:20:16.53513+08:00 INFO [539043,bdc7d47d6b583724] caller=runtime/asm_amd64.s:1581:goexit: receive module config fields:, module=monitor.ob, eventType=add, duration="5.7µs" 2023-05-18T14:20:16.53516+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:197:handleConfigEvent: pipeline event is created fields: module=monitor.ob, duration="8.4µs" 2023-05-18T14:20:16.53521+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:144:handleEvent: receive pipelie event fields: module=monitor.ob, eventType=add, duration="5.9µs" 2023-05-18T14:20:16.53524+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/plugin_instance.go:48:init: init input instance mysqlTableInput 2023-05-18T14:20:16.53905+08:00 INFO [539043,bdc7d47d6b583724] caller=mysql/table_input.go:139:Init: init mysqlTableInput with config: &{DbConnectionConfig:ocp_monitor:@tcp(127.0.0.1:2881)/oceanbase?interpolateParams=true DefaultConditionValueMap:map[ob_is_rootservice:true ob_svr_ip:10.0.10.102 ob_svr_port:2882] CollectConfigs:[0xc000230820 0xc0002308c0 0xc000230960 0xc000230a00 0xc000230aa0 0xc000230b40 0xc000230be0 0xc000230c80 0xc000230d20 0xc000230dc0 0xc000230e60 0xc000230f00 0xc000230fa0 0xc000231040 0xc0002310e0 0xc000231180 0xc000231220 0xc0002312c0 0xc000231360 0xc000231400 0xc0002314a0 0xc000231540 0xc0002315e0 0xc000231680 0xc000231720 0xc0002317c0 0xc000231860 0xc000231900 0xc0002319a0 0xc000231a40 0xc000231ae0] CollectInterval:1s TimeAlign:false} 2023-05-18T14:20:16.53987+08:00 WARN [539043,] caller=engine/pipeline.go:188:func1: init pipeline got err: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T14:20:16.5399+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:237:close: begin close input fields:, input=mysqlTableInput, duration="5.401µs" 2023-05-18T14:20:16.53992+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline.go:244:close: input closed fields:, input=mysqlTableInput, duration="26.401µs" 2023-05-18T14:20:16.53995+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:130:func1: pipeline manager handle add event failed fields:, module=monitor.ob, eventType=add, error="init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO)", duration=4.74336ms 2023-05-18T14:20:16.53997+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/pipeline_manager.go:189:handleEvent: pipeline event handle completed fields:, module=monitor.ob, eventType=add, duration=4.76276ms 2023-05-18T14:20:16.53999+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:209:handleConfigEvent: handle pipeline event compeleted fields:, module=monitor.ob, duration=4.839462ms 2023-05-18T14:20:16.54+08:00 INFO [539043,bdc7d47d6b583724] caller=engine/config_manager.go:109:schedule: module config event handle compeleted fields:, module=monitor.ob, eventType=add, duration=4.878662ms 2023-05-18T14:20:16.54001+08:00 ERROR [539043,bdc7d47d6b583724] caller=engine/pipeline_module_callback.go:40:addPipeline: add pipeline module config result status: failed, description: add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) fields:, module=monitor.ob, duration=4.981663ms 2023-05-18T14:20:16.54003+08:00 INFO [539043,bdc7d47d6b583724] caller=retry/retry.go:141:func2: execute monitor.ob 23 times, result err: add pipeline module config monitor.ob failed, description add module monitor.ob failed, reason: init module monitor.ob: init pipeline ob_basic: init input mysqlTableInput: db ping: Error 1045: Access denied for user 'ocp_monitor'@'xxx.xxx.xxx.xxx' (using password: NO) 2023-05-18T14:20:21.41003+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.682797ms 2023-05-18T14:20:21.41009+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:20:21.41019+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.469109ms 2023-05-18T14:20:21.41022+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:20:26.40978+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.9413ms 2023-05-18T14:20:26.40984+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:20:26.40991+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=16.60031ms 2023-05-18T14:20:26.40994+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:20:31.40992+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=7.8265ms 2023-05-18T14:20:31.40999+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:20:31.41005+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.929414ms 2023-05-18T14:20:31.41008+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:20:36.41061+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=7.780399ms 2023-05-18T14:20:36.41067+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:20:36.41076+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=16.878314ms 2023-05-18T14:20:36.4108+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:20:41.41101+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields:, duration=8.401806ms 2023-05-18T14:20:41.41107+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper 2023-05-18T14:20:41.41114+08:00 INFO [539043,bdc7d47d6b583724] caller=shell/exec.go:113:execute: execute shell command failed, command=Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode=1 fields: duration=17.280219ms 2023-05-18T14:20:41.41117+08:00 ERROR [539043,bdc7d47d6b583724] caller=host/custom.go:234:doCollectNtpOffset: get chronyc info failed, err: failed to execute command: Command{user=admin, program=sh, outputType=std, cmd=/usr/bin/chronyc tracking -n, timeout=50s}, exitCode: 1, output: 我们信任您已经从系统管理员那里了解了日常注意事项。 总结起来无外乎这三点： #1) 尊重别人的隐私。 #2) 输入前要先考虑(后果和风险)。 #3) 权力越大，责任越大。 sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper